Icon

Comments have been closed on this page. Please use AppMon & UEM Plugins forum for questions about this plugin.

Overview

This plugin enables monitoring of the WebSphere Data Power SOA Appliance.

Plugin Details

Plug-In Files

WebSphere DataPower Monitor Plugin v.1.0.4 (Build 6.2.0.9103)

WebSphere DataPower Monitor Plugin v.1.0.3 (Build 6.1.0.7883)

WebSphere DataPower Monitor Plugin v 4.2.0.3161

WebSphere DataPower Monitor Plugin v 4.2.0.6

Data Power Monitor Dashboard

Author

Noormohammed Sheikh
Chuck Miller (charles.miller@dynatrace.com)
Jeffrey Fynboh (jeffrey.fynboh@dynatrace.com)
Shaun Gautz (shaun.gautz@dynatrace.com)

dynaTrace Versions

4.x, 5.x, 6.0.x, 6.1.x, 6.2.x

License

dynaTrace BSD

Support

Not Supported

Known Problems

If you upgrade Datapower firmware to 7.2.0.2, you might get the error below from the DataPower Plugin.  This is a Java 7 and below issue and our Collectors run in Java 7 for version 6.2.x and most earlier supported versions as well.  If you upgrade to 6.3 which uses Java 8 under the covers, this problem should go away.  

javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair Linked Exception - Caused by: java.security.InvalidAlgorithmParameterException: Prime size must be multiple of 64, and can only range from 512 to 1024 (inclusive).

More Information
  • Latest version: 1.0.4 (Build 6.2.0.9103)
  • Consolidates all the measures from previous versions into one and fixes silly INFO logging arrayindexoutofbounds problems.

 

  • Older version: 4.2.0.6
  • Adds new Measure Groups (see below)

  • Older version: 1.0.3 (Build 6.1.0.7883)
  • Populates HCBytes/KBytes and Drop2/Error2 constructs.
  • Web Dashboard friendly Measure Group Names.

Supports only the following interfaces:

  • eth0,1,10,11,12,13,20,21
  • mgt0,1

It also handles RxHCBytes/TxHCBytes ethernet interface status responses. Drops2/Errors2 and Drops/Errors response constructs are also handled.

The plugin uses the XML Management interface as described in this PDF: SOMA_redp4446.pdf

Release History

2012-06-25 1.0.1 Initial Release

2015-03-13 1.0.2 Added support for firmware v7 (eugene.turetsky@dynatrace.com)

2015-03-13 4.2.0.3160 Added support for firmware v7, see post here. (eugene.turetsky@dynatrace.com)

2015-03-31 1.0.3 (Build 6.1.0.7883) Fixed Unit for the MemoryStatus measures.

2015-03-31 1.0.3 (Build 4.2.0.3161) Fixed Unit for the MemoryStatus measures.

2016-01-12 4.2.0.6 - Added measures for the following groups: (shaun.gautz@dynatrace.com)

ObjectStatus, SystemUsage, TCPSummary, StylesheetExecutions, DomainStatus, HTTPTransactions, and HTTPMeanTransactionTime

2016-03-15 1.0.4 (Build 6.2.0.9100) - Consolidated 4.2.0.6 measures above into a single version that also includes the per second rates.

Dashboards

The following image shows the attached dashboard including all metrics that the monitor provides:

Installation

Import the Plugin into the dynaTrace Server via the dynaTrace Server Settings menu -> Plugins -> Install Plugin. For details how to do this please refer to the dynaTrace documentation.

Available Measures

Here is the list of all Measure Groups that can currently be collected:

Availability

ConnectionsAccepted

CPUUsage

DocumentCachingSummary

DomainStatus

EnvironmentalSensors

EthernetInterfaceStatus

FileSystemStatus

HTTPConnections

HTTPTransactions

HTTPMeanTransactionTime

MemoryStatus

ObjectStatus

StylesheetCachingSummary

StylesheetExecutions

SystemUsage

TCPSummary

WSOperationMetricsSimpleIndex

 

Configuration

Name

Type

Value

Protocol

list

https

Port

long

5550

Soma Path

string

/service/mgmt/current

SOMA SOAP Envelope Template

string

HTTP Version

list

1.1

User-Agent

string

dynaTrace/6

Max. redirects

long

0

Match Content list

Disabled

 

Server authorization

Boolean

Check Box Selected

Server Username

string

The username to access data power device

Server Password

string

The password to access data power device

Proxy

Boolean

Check Box Unselected

Disable certificate Veralidation

boolean

Check Box Selected

  1. Anonymous (login to see details)

    Thanks for posting this it was very timely for a customer looking to pull in these key metrics for data power, much appreciated noor

    Mike

  2. Anonymous (login to see details)

    Great job. 

    You might want use an IBM logo on the plugin list page, and not an Oracle one ;-)

  3. Anonymous (login to see details)

    Hello, why is there not a configuration option to set the IP address of the DataPower?

    Thanks,
    Eric

    1. Anonymous (login to see details)

      I thought everyone might benefit from this email exchange on the DP Monitor ...

      Zuheir,

      Can you try to access the DataPower device external to the plugin using curl like below and let me know if that works?  The error looks to me like an empty response.  We are accessing the DataPower device through SOMA in a very similar way as curl is below …

      Get status by monitoring the device

      By changing the class attribute of the <dp:get-status> element, you can monitor different

      values of the DataPower device. This example shows the CPUUsage value.

      Request

      <?xml version="1.0" encoding="UTF-8"?>

      <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">

      <env:Body>

      <dp:request domain="default"

      xmlns:dp="http://www.datapower.com/schemas/management">

      <dp:get-status class="CPUUsage"/>

      </dp:request>

      </env:Body>

      </env:Envelope>

      Curl command

      curl -k -u user:password -d @soma_getstatus.xml https://DataPowerIP:Port/service/mgmt/current

      Response

      <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">

      <env:Body>

      <dp:response xmlns:dp="http://www.datapower.com/schemas/management">

      <dp:timestamp>2008-03-19T17:32:17+01:00</dp:timestamp>

      <dp:status>

      <CPUUsage xmlns:env="http://www.w3.org/2003/05/soap-envelope">

      <tenSeconds>5</tenSeconds>

      <oneMinute>3</oneMinute>

      <tenMinutes>6</tenMinutes>

      <oneHour>6</oneHour>

      <oneDay>6</oneDay>

      </CPUUsage>

      </dp:status>

      </dp:response>

      </env:Body>

      </env:Envelope>

      From: Zuheir AA. Al Riahy [mailto:zriahy@2p.com.sa]
      Sent: Tuesday, February 12, 2013 3:38 AM
      To: Miller, Charles
      Subject: Re: datapower plugin problem- dynatrace 5

      Hi Charles ,

      The log problem is done.

      We are facing problem trying to log to data power , they are using domain parameter  can you check if we support the domain or you use production domain by default .

      Here is the error

      ---------

      ERROR-FORMAT-STRING Exception:

      Unknown macro: {0}

      :

      Unknown macro: {1}

      java.lang.NullPointerException

      at DataPower.DataPowerMonitor.executeConnectionsAccepted(DataPowerMonitor.java:628)

      at DataPower.DataPowerMonitor.execute(DataPowerMonitor.java:297)

      at com.dynatrace.diagnostics.sdk.UserPluginManager.executePlugin(SourceFile:597)

      at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:52)

      at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:27)

      at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:192)

      at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:412)

      at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.execute(SourceFile:339)

      at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.a(SourceFile:101)

      at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.work(SourceFile:92)

      at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.executeJobInfo(SourceFile:241)

      at com.dynatrace.diagnostics.scheduling.impl.QuartzJob.execute(SourceFile:45)

      at org.quartz.core.JobRunShell.run(JobRunShell.java:202)

      at com.dynatrace.diagnostics.scheduling.impl.QuartzThreadPool$WorkerThread.run(SourceFile:788)

      ---------

      Regards,

      Sent from my iPad

       
      On Feb 11, 2013, at 5:41 PM, "Miller, Charles" <Charles.Miller@compuware.com> wrote:

      Zuheir,

      Please try the attached plugin jar (I attached it with a .txt extension to hopefully get past any email filters … just rename it to .jar).  I removed the log4j jar that is included in the plugin jar.  It looks like there is a conflict between that and some other log4j jar.

      From: Zuheir AA. Al Riahy [mailto:zriahy@2p.com.sa]
      Sent: Monday, February 11, 2013 8:07 AM
      To: Miller, Charles
      Subject: datapower plugin problem- dynatrace 5

      Hi Charles,
      Hope you are doing fine. I ‘m facing problem while trying to implement datapower plugin in one of my POCs.

      Can you please check and revert back to me .

      The detailed problem information is below ,if you need any extra info , please let me know.

      Schedule Details
      Name:   datapower
      Status:   finished
      Description:
      Type:     DataPower Monitor
      Last Run:             16:34:52 (AST)
      Last Run Result: failed
      Next Run:            -              Duration (last run):           < 1s
      Execution Offset:             5m 53s
      Schedule:             -
      Execution Target:             Embedded dynaTrace Collector
      Plugin Active:      active
      Result Status:     failed
      Result:   Last polling execution failed
      Reason for failure:           Error during execution of plug in occurred
      Error message:   Calling setup() failed

      |----------------------|
         Test Result
      |----------------------|
      Preparing test project...
      Done.
      Sending project bundle to server...
      Done.
      Preparing test run on target dynaTrace Collector@cpwr-cas...
      Done.
      Testing.........
      Test results:
      Status: 300 (Calling setup() failed)
      ERROR-FORMAT-STRING Exception:

      :

      Unknown macro: {1}

      java.lang.ExceptionInInitializerError
                    at DataPower.DataPowerMonitor.setup(DataPowerMonitor.java:289)
                    at com.dynatrace.diagnostics.sdk.UserPluginManager.executePlugin(SourceFile:487)
                    at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:52)
                    at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:27)
                    at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:192)
                    at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:412)
                    at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.execute(SourceFile:339)
                    at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.a(SourceFile:101)
                    at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.work(SourceFile:92)
                    at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.executeJobInfo(SourceFile:241)
                    at com.dynatrace.diagnostics.scheduling.impl.QuartzJob.execute(SourceFile:45)
                    at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
                    at com.dynatrace.diagnostics.scheduling.impl.QuartzThreadPool$WorkerThread.run(SourceFile:788)
      Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy.  You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy.  You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.) (Caused by org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy.  You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy.  You have more than one version of 'org.apache.commons.logging.Log' visible, which is not al...

      Best Regards,

      Zuher A.A Al Riahy
      Senior Technical Consultant
      P  :  +966 1 215 0111  E: 700
      M :  +966 5 358  72007
      zriahy@2p.com.sa<mailto:Email@2p.com.sa>
      www.2p.com.sa<http://www.2p.com.sa/>
      [cid:image001.jpg@01CE083C.B9EEFBB0]

  4. Anonymous (login to see details)

    Thanks

    That was really helpful

    Sent from my iPhone

    On Feb 14, 2013, at 17:59, "Miller, Charles" <Charles.Miller@compuware.com> wrote:

    Oh … and BTW, if you look at the SOMA SOAP Envelope Template, you will see we are using the “default” domain.  You can change that if you need to.  It is a template in the sense that we replace the with the different classes of metrics we want to retrieve from the DP device.  But you can definitely change the domain.  Hope that helps!

    <image001.png>

    <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:request domain="default" xmlns:dp="http://www.datapower.com/schemas/management"><dp:get-status class=""/></dp:request></env:Body></env:Envelope>

  5. Anonymous (login to see details)

    We just uploaded an updated version for dynaTrace 4.2+ that has better error handling built-in. Thanks to Jeff Fynboh for this contribution

  6. Anonymous (login to see details)

    Hi,

    Thank you very much for this plug-in.

    There are multiple domains on a single datapower device, at my account. The customer asked me if it would be possible to retrieve the metrics of each individual domain.

    From my understanding, the plug-in currently retrieves the metrics for the overall datapower device. Please let me know if this is possible.

    Regards,

    Harshal.

  7. Anonymous (login to see details)

    I am working to configure and use this plugin and it seems pretty helpful.  For some reason, I am not able to display the CPU Usage numbers - the graph says no measures available.  I am able to see the Memory usage, but would like to see CPU usage as well.  I'm also not seeing the connection counts - I believe it may be one fix that would correct that and the CPU, but I'm not sure.

    When I tried the curl command above - I get a Malformed Content error.

    I was able to get past the Malformed Content error - I get no data returned for CPUUsage, I see expected values for MemoryStatistics.  I'll get with my DataPower folks to see if they can help explain why.

     

    This was ultimately resolved by enabling Statistics on the default domain.  I mis understood that I would get MemoryStatistics, but not CPUUsage when statistics were disabled.

     

    1. Anonymous (login to see details)

      Hi Mike, we are not seeing the CPUUsage data as well.. How and where do you enable Statistics?

      1. Anonymous (login to see details)

        Hi Raphael,

        Log on to the DataPower WEB GUI, then go to

        Objects-->System–>Statistic settings. You can enable Statistics from there.

        Regards,

        Harshal.

  8. Anonymous (login to see details)

    The plugin is not getting the status of the Ethernet interfaces on our device.  The plugin has out of the box measures for ETH1 and ETH2, but our device uses ETH10 and ETH11.

    I have tried to modify the existing or create a new measure, but the measure specific attributes section is greyed out.  How can I create a new measure that gets data from a different ETH port?

  9. Anonymous (login to see details)

    John,

    If you can provide the version of the DataPower plugin you are using?  I will check it out.

    Thanks!

    Chuck

    1. Anonymous (login to see details)

      Plugin version 4.2.0.3154

      Here is a screenshot of what I see.  I can modify the measure name, but I am not able to modify what the measure points to.

       

  10. Anonymous (login to see details)

    John,

    Can you please try the updated DP Plugin at the following URL ...

    https://dl.dropboxusercontent.com/u/30563453/com.dynatrace.diagnostics.plugin.DataPowerMonitor_4.2.0.3155.jar

    And let me know how that works.  If it works, I will post it.

    Thanks!

    Chuck

    1. Anonymous (login to see details)

      The update did not allow me to modify the measure.

  11. Anonymous (login to see details)

    John,

    You shouldn't need to modify any measures.  The new measures for eth10 and eth11 should be there in the measure list (see screenshot below).  I updated the plugin, added these new measures and changed the code to populate them.

    Let me know if you don't see them in your list.

    Thanks!

    Chuck

  12. Anonymous (login to see details)

    I mis-understood the update.  I recreated the monitor and it has the new measures for ETH10 and 11, but they are reporting NULL.

    Thank you

  13. Anonymous (login to see details)

    they do show up when I run curl against the datapower boxes

  14. Anonymous (login to see details)

    John,

    Let's have a session together on this.  Can you provide your direct email and I will set it up.

    Thanks!

    Chuck

    1. Anonymous (login to see details)

       

      Just emailed it to you.

  15. Anonymous (login to see details)

    I'm trying to understand the correlation between response complete time and first response delay and I'm not sure what first response delay is telling me.  I notice that my response complete time is often just barely larger than the first response delay - I just don't know if that is normal, expected behavior.

  16. Anonymous (login to see details)

    We are upgrading our DataPower firmware to the v7 base - should we experience any issues with the plugin at that firmware level?  We are moving from the v5 firmware level.

    1. Anonymous (login to see details)

      Hi Mike,

      Plugin should not be affected by the firmware upgrade. However, the safe way to do an upgrade is to apply it first to your test environment hardware, test plugin there and then on success rollout firmware upgrade to the rest of your infrastructure.

      Please let us know in case you encounter any issues with the plugin after you upgrade firmware of the DataPower boxes to version 7.x.

      Eugene.

      1. Anonymous (login to see details)

        That is our plan.  We updated the firmware on our Dev device this morning, so I'm setting up monitoring of it now to see if it works.  So far I'm having issues, but I had not monitored this device before the upgrade either.  I have heard that information is reported to our syslog server differently with this firmware than what we were running, but I do not know if that is causing my issues or not yet.  I will keep you posted as I continue looking at it.

        1. Anonymous (login to see details)

          Hi Mike,

          Sounds good. Keep us updated if plugin has any issues after the firmware upgrade.

           Eugene.

          1. Anonymous (login to see details)

             The error we are seeing is:

            2015-03-10 09:52:20 INFO [DataPowerMonitor@Dev DataPower Monitor_0] Populating Connections Accepted Measures ...
            2015-03-10 09:52:20 INFO [DataPowerMonitor@NonProduction DataPower Monitor_0] Populating Connections Accepted Measures ...
            2015-03-10 09:52:20 WARNING [DataPowerMonitor@Dev DataPower Monitor_0] Parsing httpVersion failed, using default: HTTP/1.1
            2015-03-10 09:52:20 INFO [DataPowerMonitor@NonProduction DataPower Monitor_0] Executing method: POST, URI: https://10.200.12.100:5550/service/mgmt/current, SOAP Envelope: <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:request domain="default" xmlns:dp="http://www.datapower.com/schemas/management"><dp:get-status

            class="ConnectionsAccepted"/></dp:request></env:Body></env:Envelope>
            2015-03-10 09:52:20 INFO [DataPowerMonitor@Dev DataPower Monitor_0] Executing method: POST, URI: https://10.207.80.104:5550/service/mgmt/current, SOAP Envelope: <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:request domain="default" xmlns:dp="http://www.datapower.com/schemas/management"><dp:get-status class="ConnectionsAccepted"/></dp:request></env:Body></env:Envelope>

            We are not seeing any exceptions on the DataPower side itself, it is showing completed connections in that log.

            1. Anonymous (login to see details)

              Hi Mike,

              Could you please send me directly a complete plugin log file? My e-mail address is eugene.turetsky@Compuware.com. You may zip the log file before attaching to e-mail. Also include multiple generations of the plugin log files.

              Eugene. 

              1. Anonymous (login to see details)

                Hi

                This morning we updated the firmware on our datapower device from 7.1.0.4  to 7.2.0.0 , after the update the plugin has stopped working

                On the DP device we are seeing

                SSL library error: error:140940E5 SL routines sl3_read_bytes sl handshake failure
                ssl3_read_bytes
                ssl handshake failure
                I can send you the plugin logs for the period of the upgrade of firmware
                Thanks
                1. Anonymous (login to see details)

                  Hi Jason,

                  Please let me know version of the plugin that you are using. Please also set log level of the plugin to FINER and e-mail me plugin's log file at eugene.turetsky@dynatrace.com.

                  Eugene.

  17. Anonymous (login to see details)

    I setup this plugin to create an alert when the datapower device goes down. I thought I could use the HostReachable or HttpStatusCode metrics. When the datapower device was down, the monitor failed to execute, which means the charts were empty during that time. Is this how the plugin should work?

    1. Anonymous (login to see details)

      If this doesn't work, maybe just try a URL monitor? This one may not fail gracefully when it can't connect to the XML Management Interface.

      1. Anonymous (login to see details)

        Yes, that is what I ended up doing. The HostReachable metric on the URL monitor plugin gives me a 0 when the device is down.

        1. Anonymous (login to see details)

          Hi Shaun,

          Please pay attention to the HostReachable metric of the URL monitor. It does not differentiate between host is down or host is up but web server on the host is down.

          Eugene.

  18. Anonymous (login to see details)

    Hello,

    Do we have capability to monitor Datapower little more in depth? i.e. to capture the web requests, response time, failures, errors etc. I think using this plugin we will get the system level information only.

    Please let me know.

    Thanks.

    1. Anonymous (login to see details)

      Hi Madhu,

      We can add new features to the Data Power plugin. Please send me e-mail to eugene.turetsky@dynatrace.com to finalize your request.

      Eugene.

      1. Anonymous (login to see details)

        Hi Eugene,

        Is there a list of features you are currently working on for this plugin? I don't want to duplicate Madhu's request.

        Thanks!

        Jake

        1. Anonymous (login to see details)

          Hi Jake,

          I have never received any specific requests from Madhu.

          Eugene.

          1. Anonymous (login to see details)

            Hello Eugene,

            We were going through the list of attributes that we need and came up with the below. Ideally we would like the plugin to capture the transactions at the API level. Not sure if it can do that.

            Here is the list:

            ActiveUsers
            DomainStatus
            EthernetInterfaceStatus
            FilesystemStatus
            FirmwareStatus
            FirmwareVersion
            MemoryStatus
            CPUUsage
            MessageCounts
            MessageDurations
            MessageSources
            StylesheetExecutions
            TCPSummary

            Can you please update the plugin to accommodate these? Let me know if you have any questions. 

            Thank you very much for your help.
             

            Thanks,
            Madhu

            1. Anonymous (login to see details)

              Hi Madhu,

              Thank you for the list of features that you are looking for. Let's see what we can do to enhance current version of the plugin. I'll update you.

              Eugene.

            2. Anonymous (login to see details)

              See version 4.2.0.6 above. Many of these are now in the plugin.

  19. Anonymous (login to see details)

    Today we used this plugin 'WebSphere DataPower Monitor Plugin v.1.0.3 (Build 6.1.0.7883)' and the Monitor executed 'successfully', but was returning NULL values for all Measures/metrics.  Upon further investigation, the password for the username was incorrect.  Once we fixed the password, the Measures reported the actual values.  I would think that an incorrect password would return some sort of error on the plugin side.  Even the log file file was clean.  Is this happening for anyone else?

    1. Anonymous (login to see details)

      Hi Tony,

      If you change the log level of the plugin to "FINE", for the SOAP request, one of the parameters returned is "Authentication Failure".

      That's an indication of an incorrect username/password.

      Hope this helps.

      -Harshal.

    2. Anonymous (login to see details)

      Hi Anthony,

      Thank you for your feedback. We will look into it. If you setup the FINE log level of the DataPower plugin you should see the "<dp:result>Authentication failure</dp:result>" string in the reply SOAP message.

      To make sure we are taking right actions here, could you please set plugin's log level to FINE, reproduce the problem and send me gathered plugin log file at eugene.turetsky@dynatrace.com?

      Eugene.

       

  20. Anonymous (login to see details)

    Hi Tony,

    The plugin is built off of the HTTP Monitor code and therefore checks for HTTP errors and/or timeouts.  Even though the overall operation was unsuccessful due to authentication, "technically" it executed a successful SOAP request/response to the DP device.  I agree, though, that as we are already parsing the response, we should check for "Authentication failure" and report the error accordingly.  @Eugene, does that make sense?

    Thanks!

     

    Chuck

    1. Anonymous (login to see details)

      Hi Chuck,

      You are correct, the HTTP status code is "HTTP/1.1 200 Good[\r][\n]" in case when we have authentication failure. So, plugin needs to parse returned message to identify success or failure of the SOAP request. I'll run it by IBM team because I think we could have other cases when request is failing but HTTP status code is 200. In general, I'd expect to see SOAP fault response.

      Eugene.

  21. Anonymous (login to see details)

    Hello,

    My customer loves the plugin so far, they are wondering what steps would have to be taken to add another particular datapower metric to return as a measure in dynatrace. The datapower metric they are interested in is known as system usage as mentioned below.

    Here is the show load info

    Web GUI

    System => System Usage

    XMI

    SystemUsage/Load

    CLI

    Show Load

    Status MIB

    dpStatusSystemUsageLoad

    Source

    System Usage is a measurement of the device’s ability to accept additional work. It is a formulaic calculation based on various components of system load. System Usage is typically considered the best single indicator of overall system capacity. While it may sometimes spike to 100%, typical values are less than 75%. The secondary work list value is a calculation of queued tasks, and is of lesser interest in typical monitoring situations.

    An interesting note is that underlined sentence that states that this particular metric is deemed a great indicator of overall system capacity. Im not sure what scope of work would need to be done to get this particular metric added, but it seems like a good one to add overall if possible.  Any information would be more than helpful. Thanks.


     

    1. Anonymous (login to see details)

      Hello Nathan,

      were you able to figure out how to add more metrics/measure to the plugin?

    2. Anonymous (login to see details)

      See version 4.2.0.6 above. I added SystemUsage Load.

  22. Anonymous (login to see details)

    Hello,

    I have a customer who wants to use this plugin to monitor their data power device. I have never used this plugin before and I'm not really sure how to configure it.

    I understand the protocol and port but what is the plugin looking for in the SOMA Path and SOMA SOAP Envelope Template? Once the plugin is configured (assuming correctly), is the Monitors (under a system profile) used to gather the data and then use the dashboard the view it? Sorry I am just confused on how this works and the customer really wants to use this plugin.

     

    Thanks!

  23. Anonymous (login to see details)

    Brian,

    The SOMA path is the path to the Datapower appliance management interface where their statistics are exposed.  The overall URI would look something like this ...

    https://<datapower appliance address>/service/mgmt/current:5500

    The SOMA management interface of the Datapower appliance expects to receive a SOAP envelope as part of any http/s posts that will be sent.  The content of the SOAP envelope is for the most part represented in the SOMA SOAP Envelope Template.  The way that works is the @SOMAMONITORCLASS@ is a placeholder in the template (and why it is called a template) and is substituted at runtime for each of the SOMA classes that we are retrieving statistics on (i.e. ConnectionAccepted, CPUUsage, EthernetInterfaceStatus, etc ...).  Below is the runtime example for CPUUsage. You need not change the default unless IBM changes the SOMA interface or you are interested in other domains.

    <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:request domain="default"xmlns:dp="http://www.datapower.com/schemas/management"><dp:get-status class="CPUUsage"/></dp:request></env:Body></env:Envelope>

    The SOMA SOAP Envelope Template also allows the domain to be specified if there is interest in any domains other than "default".

    See http://www.redbooks.ibm.com/redpapers/pdfs/redp4446.pdf for more detail on the Datapower SOMA interface.

    Hope that helps.

    Thanks!

     

    Chuck

  24. Anonymous (login to see details)

    Oh ... and of course once the plugin is installed onto the Dt Server, you would need to set it up to run under the Monitors of a given profile and point it to a given Datapower device (host) or set of devices (host group).  Once that is done, the measures will be created and the values stored in the Performance Warehouse and then be available to chart, threshold, alert, etc ...

    Hope that helps.

    Thanks!

    Chuck

  25. Anonymous (login to see details)

    Hello,

    Has anyone added more measures more than what comes with the plugin? 

    this is by default:

    // measure constants
    "AvailabilityMeasures";
    "ConnectionsAcceptedMeasures";
    "CPUUsageMeasures";
    "DocumentCachingSummaryMeasures";
    "StylesheetCachingSummaryMeasures";
    "EnvironmentalSensorsMeasures";
    "HTTPConnectionsMeasures";
    "MemoryStatusMeasures";
    "FileSystemStatusMeasures";
    "EthernetInterfaceStatusMeasures";

    1. Anonymous (login to see details)

      See version 4.2.0.6 above

  26. Anonymous (login to see details)

    Hi guys,

    I tried running the monitor but it failed... inspecting the logs gave me the following entries

    2016-03-01 15:31:55 WARNING [DataPowerMonitor@Staging DataPower Monitor_0] Previous message was repeated 1 times.
    2016-03-01 15:31:55 WARNING [DataPowerMonitor@Staging DataPower Monitor_0] Parsing httpVersion failed, using default: HTTP/1.1
    2016-03-01 15:31:55 INFO [DataPowerMonitor@Staging DataPower Monitor_0] Executing method: POST, URI: https://10.200.76.177:5550/service/mgmt/current, SOAP Envelope: <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:request domain="default" xmlns:dp="http://www.datapower.com/schemas/management"><dp:get-status class="ConnectionsAccepted"/></dp:request></env:Body></env:Envelope>
    2016-03-01 15:32:03 SEVERE [DataPowerMonitor@Staging DataPower Monitor_0] null: java.lang.RuntimeException: Could not generate DH keypair
    2016-03-01 15:32:03 INFO [DataPowerMonitor@Staging DataPower Monitor_0] Setting response code to 503 due to IOException: : java.lang.RuntimeException: Could not generate DH keypair
    2016-03-01 15:32:03 INFO [DataPowerMonitor@Staging DataPower Monitor_0] Populating Availability Measures ...
    2016-03-01 15:32:03 INFO [DataPowerMonitor@Staging DataPower Monitor_0] Populating CPU Usage Measures ...
    2016-03-01 15:32:03 INFO [DataPowerMonitor@Staging DataPower Monitor_0] Executing method: POST, URI: https://10.200.76.177:5550/service/mgmt/current, SOAP Envelope: <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:request domain="default" xmlns:dp="http://www.datapower.com/schemas/management"><dp:get-status class="CPUUsage"/></dp:request></env:Body></env:Envelope>

    The "Could not generate DH keypair" message caught my attention. Is there something I am missing out?

    1. Anonymous (login to see details)

      Hi Eugene, Shaun

      Any input here? Its an SSL issue related to the Diffie Hellman key. Would upgrading Java help?

      Thanks,

      Harshal.

      1. Anonymous (login to see details)

        I'm having the same error with the DH key.

        2016-09-29 14:06:27 WARNING [DataPowerMonitor@Enterprise_eSOA_XXX_0] Previous message was repeated 10 times.

        2016-09-29 14:06:27 WARNING [DataPowerMonitor@Enterprise_eSOA_XXX_0] Parsing httpVersion failed, using default: HTTP/1.1

        2016-09-29 14:06:27 INFO [DataPowerMonitor@Enterprise_eSOA_XXX_0] Executing method: POST, URI: https://XX.XX.XX.XX:5550/service/mgmt/current, SOAP Envelope: <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:request domain="default" xmlns:dp="http://www.datapower.com/schemas/management"><dp:get-status class="ConnectionsAccepted"/></dp:request></env:Body></env:Envelope>

        2016-09-29 14:06:27 SEVERE [DataPowerMonitor@Enterprise_eSOA_XXX_0] null: Connection refused

        2016-09-29 14:07:27 INFO [DataPowerMonitor@Enterprise_eSOA_XXX_0] Populating Connections Accepted Measures for XX.XX.XX.XX ->https://XX.XX.XX.XX:5550/service/mgmt/current

        2016-09-29 14:07:27 INFO [DataPowerMonitor@Enterprise_eSOA_XXX_0] Executing method: POST, URI: https://XX.XX.XX.XX:5550/service/mgmt/current, SOAP Envelope: <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:request domain="default" xmlns:dp="http://www.datapower.com/schemas/management"><dp:get-status class="ConnectionsAccepted"/></dp:request></env:Body></env:Envelope>

        2016-09-29 14:08:27 INFO [DataPowerMonitor@Enterprise_eSOA_XXX_0] Populating Connections Accepted Measures for XX.XX.XX.XX ->https://XX.XX.XX.XX:5550/service/mgmt/current

        2016-09-29 14:08:27 INFO [DataPowerMonitor@Enterprise_eSOA_XXX_1] Populating Connections Accepted Measures for XX.XX.XX.XX ->null

        2016-09-29 14:08:27 INFO [DataPowerMonitor@Enterprise_eSOA_XXX_0] Executing method: POST, URI: https://XX.XX.XX.XX:5550/service/mgmt/current, SOAP Envelope: <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:request domain="default" xmlns:dp="http://www.datapower.com/schemas/management"><dp:get-status class="ConnectionsAccepted"/></dp:request></env:Body></env:Envelope>

        2016-09-29 14:08:27 WARNING [DataPowerMonitor@Enterprise_eSOA_XXX_1] Parsing httpVersion failed, using default: HTTP/1.1

        2016-09-29 14:08:27 INFO [DataPowerMonitor@Enterprise_eSOA_XXX_1] Executing method: POST, URI: https://XX.XX.XX.XX:5550/service/mgmt/current, SOAP Envelope: <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:request domain="default" xmlns:dp="http://www.datapower.com/schemas/management"><dp:get-status class="ConnectionsAccepted"/></dp:request></env:Body></env:Envelope>

        2016-09-29 14:08:27 SEVERE [DataPowerMonitor@Enterprise_eSOA_XXX_1] null: java.lang.RuntimeException: Could not generate DH keypair

         What is the recommended resolution for this type of error?

  27. Anonymous (login to see details)

    Hi Chuck,

     

    We setup the plugin in our environment. The monitor running successfully. But we get no measures in the dashboard. Could you kindly please help on look into it?

     

    I attached the log file and screen shot for your review.

     

    2016-03-15_09h37_36.png

     

    com.dynatrace.diagnostics.plugin.DataPowerMonitor.monitor.0.0.log

     

    Thanks

    YC

    1. Anonymous (login to see details)

      Hi YC Ma

      Thank you for providing the logs. In the logs, I see that a number of "authentication failure" messages, meaning that the user name and password that you are using is not able to retrieve metrics from DataPower. Please see the screenshot below:

       

       

      Hope this helps,

      Harshal.

  28. Anonymous (login to see details)

    Hi , 

    i have installed the latest version of plugin and got the below error message. i deleted the plugin and the tasks in the tasks and monitor section.

     

    when i reinstalled the plugin am not seeing the datapower task any more. can you please help on how to recreate the monitor tasks

     

    15:20:35 WARNING [UserPluginManager] java.lang.StringIndexOutOfBoundsException - String index out of range: 750
    java.lang.StringIndexOutOfBoundsException: String index out of range: 750
    at java.lang.String.substring(String.java:1963)
    at DataPower.DataPowerMonitor.executeDocumentCachingSummary(DataPowerMonitor.java:1019)
    at DataPower.DataPowerMonitor.execute(DataPowerMonitor.java:551)
    at com.dynatrace.diagnostics.sdk.UserPluginManager.a(SourceFile:720)
    at com.dynatrace.diagnostics.sdk.UserPluginManager.b(SourceFile:478)
    at com.dynatrace.diagnostics.sdk.UserPluginManager.executePlugin(SourceFile:278)
    at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:50)
    at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:26)
    at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.a(SourceFile:190)
    at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.a(SourceFile:413)
    at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.execute(SourceFile:337)
    at com.dynatrace.diagnostics.schedule.SchedulerJob.a(SourceFile:101)
    at com.dynatrace.diagnostics.schedule.SchedulerJob.work(SourceFile:92)
    at com.dynatrace.diagnostics.schedule.SchedulerJob.executeJobInfo(SourceFile:241)
    at com.dynatrace.diagnostics.schedule.QuartzJob.execute(SourceFile:45)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
    at com.dynatrace.diagnostics.schedule.QuartzThreadPool$WorkerThread.run(SourceFile:788)

  29. Anonymous (login to see details)

    Ajay,

    Please try the following updated version 9101.  It should work fine now.

    com.dynatrace.diagnostics.plugin.DataPowerMonitor_6.2.0.9101.jar

    Sorry for the inconvenience.

    Chuck

  30. Anonymous (login to see details)

    Chuck,

    installed the latest version getting the below error now

     

    2016-04-07 10:26:06 WARNING [UserPluginManager] java.lang.StringIndexOutOfBoundsException - String index out of range: 300
    java.lang.StringIndexOutOfBoundsException: String index out of range: 300
    at java.lang.String.substring(String.java:1963)
    at DataPower.DataPowerMonitor.executeConnectionsAccepted(DataPowerMonitor.java:879)
    at DataPower.DataPowerMonitor.execute(DataPowerMonitor.java:548)
    at com.dynatrace.diagnostics.sdk.UserPluginManager.a(SourceFile:720)
    at com.dynatrace.diagnostics.sdk.UserPluginManager.b(SourceFile:478)
    at com.dynatrace.diagnostics.sdk.UserPluginManager.executePlugin(SourceFile:278)
    at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:50)
    at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:26)
    at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.a(SourceFile:190)
    at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.a(SourceFile:413)
    at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.execute(SourceFile:337)
    at com.dynatrace.diagnostics.schedule.SchedulerJob.a(SourceFile:101)
    at com.dynatrace.diagnostics.schedule.SchedulerJob.work(SourceFile:92)
    at com.dynatrace.diagnostics.schedule.SchedulerJob.executeJobInfo(SourceFile:241)
    at com.dynatrace.diagnostics.schedule.QuartzJob.execute(SourceFile:45)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
    at com.dynatrace.diagnostics.schedule.QuartzThreadPool$WorkerThread.run(SourceFile:788)

  31. Anonymous (login to see details)

    we running on dynatrace 6.3

    1. Anonymous (login to see details)

      Ajay,

      Sorry we weren't able to connect today.  Believe it or not, the indexoutofboundsexception was just poorly orchestrated INFO logging.  Somehow I missed one of the metric types in the previous fix.  This one should do the trick.  

      com.dynatrace.diagnostics.plugin.DataPowerMonitor_6.2.0.9102.jar

      And again ... sorry for the inconvenience.

      Thanks!

       

      Chuck

    2. Anonymous (login to see details)

      How are we doing out there Ajay? All good? (smile)

  32. Anonymous (login to see details)

    So far good Chuck , is there anyway we can get purepaths from this plugin.

  33. Anonymous (login to see details)

    Ajay,

    Unfortunately, there is no way to inject ourselves into the DataPower path.  But do take a look at the Observed Tier capability we introduced in 6.3.  DataPower was a big part of the design center for this feature.  It isn't purepath detail about DataPower, but I think it can get you pretty close to what you are looking for ...

    Observed Tiers

    Thanks!

    Chuck

  34. Anonymous (login to see details)

    Folks,

    Just a heads up ...

    If you upgrade Datapower firmware to 7.2.0.2, you might get the error below from the DataPower Plugin.  This is a Java 7 and below issue and our Collectors run in Java 7 for version 6.2.x and most earlier supported versions as well.  If you upgrade to 6.3 which uses Java 8 under the covers, this problem should go away.  

    javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair Linked Exception - Caused by: java.security.InvalidAlgorithmParameterException: Prime size must be multiple of 64, and can only range from 512 to 1024 (inclusive).

    Thanks!

    Chuck

    1. Anonymous (login to see details)

      I was just about to present this issue on the page here, and spotted this instead.  Chuck can you get the plugin info update above to list this? maybe in the "more information" section.  Thanks for posting this.

  35. Anonymous (login to see details)

    We were getting the SSL error after the DataPower upgrade, but that went away after our dynaTrace 6.3 update. Now we are still not getting any data from the DataPower devices. The plugin log doesn't have any errors, but shows the connection opening and then closing. There are related Java errors in the Collector log:

     

    2016-04-25 13:29:20 WARNING [UserPluginManager] java.lang.NullPointerException - null
    java.lang.NullPointerException
     at com.dynatrace.diagnostics.sdk.plugins.logging.CompressingFileHandler.publish(SourceFile:40)
     at com.dynatrace.diagnostics.sdk.plugins.logging.DelegationHandler.publish(SourceFile:115)
     at com.dynatrace.diagnostics.util.modern.LogManager$ContextLogger.log(LogManager.java:220)
     at java.util.logging.Logger.doLog(Logger.java:765)
     at java.util.logging.Logger.log(Logger.java:875)
     at DataPower.DataPowerMonitor.callDPSOMAMethod(DataPowerMonitor.java:2989)
     at DataPower.DataPowerMonitor.executeConnectionsAccepted(DataPowerMonitor.java:873)
     at DataPower.DataPowerMonitor.execute(DataPowerMonitor.java:548)
     at com.dynatrace.diagnostics.sdk.UserPluginManager.a(SourceFile:720)
     at com.dynatrace.diagnostics.sdk.UserPluginManager.b(SourceFile:478)
     at com.dynatrace.diagnostics.sdk.UserPluginManager.executePlugin(SourceFile:278)
     at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:50)
     at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:26)
     at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.a(SourceFile:190)
     at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.a(SourceFile:413)
     at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.execute(SourceFile:337)
     at com.dynatrace.diagnostics.schedule.SchedulerJob.a(SourceFile:101)
     at com.dynatrace.diagnostics.schedule.SchedulerJob.work(SourceFile:92)
     at com.dynatrace.diagnostics.schedule.SchedulerJob.executeJobInfo(SourceFile:241)
     at com.dynatrace.diagnostics.schedule.QuartzJob.execute(SourceFile:45)
     at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
     at com.dynatrace.diagnostics.schedule.QuartzThreadPool$WorkerThread.run(SourceFile:788)

     

    Any suggestions?

     

    thanks!

     

    1. Anonymous (login to see details)

      Sorry for the late reply Dave.  Can you provide the log from the DataPower plugin execution itself?  If there is little there to go by, you can change the logging to finest from the DT Server->Plugins->DataPower Monitor properties and provide that log file.  Depending on what that yields, we may need to see about it together.

      Thanks!

      Chuck

      1. Anonymous (login to see details)

        Sure, here are the relevant lines excerpted from a log for a manual run of the monitors against 4 devices that worked in the past (I've masked out the auth string).

         


         

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_1] Executing DataPowerMonitor ...10.40.1.14 ->

        https://10.40.1.14:5550/service/mgmt/current 

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_1] *******************************************************************1

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_1] *******************************************************************2

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_1] *******************************************************************3

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_1] Populating Connections Accepted Measures for 10.40.1.14 ->

        https://10.40.1.14:5550/service/mgmt/current 

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_0] Executing DataPowerMonitor ...10.76.40.6 ->

        https://10.76.40.6:5550/service/mgmt/current 

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_0] *******************************************************************1

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_0] *******************************************************************2

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_0] *******************************************************************3

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_2] Executing DataPowerMonitor ...10.76.40.3 ->

        https://10.76.40.3:5550/service/mgmt/current 

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_2] *******************************************************************1

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_2] *******************************************************************2

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_2] *******************************************************************3

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_0] Populating Connections Accepted Measures for 10.76.40.6 ->

        https://10.76.40.6:5550/service/mgmt/current 

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_2] Populating Connections Accepted Measures for 10.76.40.3 ->

        https://10.76.40.3:5550/service/mgmt/current 

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_3] Executing DataPowerMonitor ...10.40.1.16 ->

        https://10.40.1.16:5550/service/mgmt/current 

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_3] *******************************************************************1

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_3] *******************************************************************2

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_3] *******************************************************************3

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_3] Populating Connections Accepted Measures for 10.40.1.16 ->

        https://10.40.1.16:5550/service/mgmt/current 

        2016-05-06 13:46:37 FINE [DataPowerMonitor@DataPower DEMO_2] auth string: *******

        2016-05-06 13:46:37 FINE [DataPowerMonitor@DataPower DEMO_1] auth string: *******

        2016-05-06 13:46:37 FINE [DataPowerMonitor@DataPower DEMO_3] auth string: *******

        2016-05-06 13:46:37 FINE [DataPowerMonitor@DataPower DEMO_0] auth string: *******

        2016-05-06 13:46:37 FINE [DataPowerMonitor@DataPower DEMO_0] Base64 encoded auth string: Q211dHVhbFxTQS1EYXRhcG93ZXItUU1DLU06N3EyMEJnMFRNTGRzbA==

        2016-05-06 13:46:37 FINE [DataPowerMonitor@DataPower DEMO_1] Base64 encoded auth string: Q211dHVhbFxTQS1EYXRhcG93ZXItUU1DLU06N3EyMEJnMFRNTGRzbA==

        2016-05-06 13:46:37 FINE [DataPowerMonitor@DataPower DEMO_3] Base64 encoded auth string: Q211dHVhbFxTQS1EYXRhcG93ZXItUU1DLU06N3EyMEJnMFRNTGRzbA==

        2016-05-06 13:46:37 FINE [DataPowerMonitor@DataPower DEMO_2] Base64 encoded auth string: Q211dHVhbFxTQS1EYXRhcG93ZXItUU1DLU06N3EyMEJnMFRNTGRzbA==

        2016-05-06 13:46:37 WARNING [DataPowerMonitor@DataPower DEMO_2] Previous message was repeated 1 times.

        2016-05-06 13:46:37 WARNING [DataPowerMonitor@DataPower DEMO_2] Parsing httpVersion failed, using default: HTTP/1.1

        2016-05-06 13:46:37 WARNING [DataPowerMonitor@DataPower DEMO_3] Previous message was repeated 1 times.

        2016-05-06 13:46:37 WARNING [DataPowerMonitor@DataPower DEMO_3] Parsing httpVersion failed, using default: HTTP/1.1

        2016-05-06 13:46:37 WARNING [DataPowerMonitor@DataPower DEMO_0] Previous message was repeated 1 times.

        2016-05-06 13:46:37 WARNING [DataPowerMonitor@DataPower DEMO_0] Parsing httpVersion failed, using default: HTTP/1.1

        2016-05-06 13:46:37 WARNING [DataPowerMonitor@DataPower DEMO_1] Previous message was repeated 1 times.

        2016-05-06 13:46:37 WARNING [DataPowerMonitor@DataPower DEMO_1] Parsing httpVersion failed, using default: HTTP/1.1

        2016-05-06 13:46:37 FINE [DefaultHttpParams@DataPower DEMO_2] Set parameter http.protocol.version = HTTP/1.1

        2016-05-06 13:46:37 FINE [DefaultHttpParams@DataPower DEMO_0] Set parameter http.protocol.version = HTTP/1.1

        2016-05-06 13:46:37 FINE [DefaultHttpParams@DataPower DEMO_1] Set parameter http.protocol.version = HTTP/1.1

        2016-05-06 13:46:37 FINE [DefaultHttpParams@DataPower DEMO_3] Set parameter http.protocol.version = HTTP/1.1

        2016-05-06 13:46:37 FINE [DefaultHttpParams@DataPower DEMO_1] Set parameter http.protocol.max-redirects = 0

        2016-05-06 13:46:37 FINE [DefaultHttpParams@DataPower DEMO_3] Set parameter http.protocol.max-redirects = 0

        2016-05-06 13:46:37 FINE [DefaultHttpParams@DataPower DEMO_1] Set parameter http.method.retry-handler = DataPower.DataPowerMonitor$1@4f33a819

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_1] Executing method: POST, URI:

        https://10.40.1.14:5550/service/mgmt/current , SOAP Envelope: <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:request domain="default" xmlns:dp="http://www.datapower.com/schemas/management"><dp:get-status class="ConnectionsAccepted"/></dp:request></env:Body></env:Envelope>

        2016-05-06 13:46:37 FINE [HttpConnection@DataPower DEMO_1] Open connection to 10.40.1.14:5550

        2016-05-06 13:46:37 FINE [DefaultHttpParams@DataPower DEMO_3] Set parameter http.method.retry-handler = DataPower.DataPowerMonitor$1@1e1061e7

        2016-05-06 13:46:37 FINE [DefaultHttpParams@DataPower DEMO_0] Set parameter http.protocol.max-redirects = 0

        2016-05-06 13:46:37 FINE [DefaultHttpParams@DataPower DEMO_2] Set parameter http.protocol.max-redirects = 0

        2016-05-06 13:46:37 FINE [DefaultHttpParams@DataPower DEMO_0] Set parameter http.method.retry-handler = DataPower.DataPowerMonitor$1@4e3e27da

        2016-05-06 13:46:37 FINE [DefaultHttpParams@DataPower DEMO_2] Set parameter http.method.retry-handler = DataPower.DataPowerMonitor$1@12eb691d

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_3] Executing method: POST, URI:

        https://10.40.1.16:5550/service/mgmt/current , SOAP Envelope: <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:request domain="default" xmlns:dp="http://www.datapower.com/schemas/management"><dp:get-status class="ConnectionsAccepted"/></dp:request></env:Body></env:Envelope>

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_2] Executing method: POST, URI:

        https://10.76.40.3:5550/service/mgmt/current , SOAP Envelope: <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:request domain="default" xmlns:dp="http://www.datapower.com/schemas/management"><dp:get-status class="ConnectionsAccepted"/></dp:request></env:Body></env:Envelope>

        2016-05-06 13:46:37 FINE [HttpConnection@DataPower DEMO_3] Open connection to 10.40.1.16:5550

        2016-05-06 13:46:37 INFO [DataPowerMonitor@DataPower DEMO_0] Executing method: POST, URI:

        https://10.76.40.6:5550/service/mgmt/current , SOAP Envelope: <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:request domain="default" xmlns:dp="http://www.datapower.com/schemas/management"><dp:get-status class="ConnectionsAccepted"/></dp:request></env:Body></env:Envelope>

        2016-05-06 13:46:37 FINE [HttpConnection@DataPower DEMO_2] Open connection to 10.76.40.3:5550

        2016-05-06 13:46:37 FINE [HttpConnection@DataPower DEMO_0] Open connection to 10.76.40.6:5550

        2016-05-06 13:46:58 SEVERE [DataPowerMonitor@DataPower DEMO_3] null: Connection timed out: connect

        2016-05-06 13:46:58 SEVERE [DataPowerMonitor@DataPower DEMO_0] null: Connection timed out: connect

        2016-05-06 13:46:58 SEVERE [DataPowerMonitor@DataPower DEMO_2] null: Connection timed out: connect

        2016-05-06 13:46:58 SEVERE [DataPowerMonitor@DataPower DEMO_1] null: Connection timed out: connect

  36. Anonymous (login to see details)

    Hmmm ... looks like a problem making a connection to the devices over https.  Has this worked in the past?  Could the connection be blocked from the collector machine?  All of these connections are timing out.  Can you try using curl or wget from the collector machine and see if that is successful?  If that works, then something is wrong with the plugin.  If not, it is likely firewall blockage.  

    Here's an example of using curl.  If you get a response like below, then we need to look at it together.

    Request (embed this XML into soma_getstatus.xml and reference like below)

    <?xml version="1.0" encoding="UTF-8"?>

    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">

    <env:Body>

    <dp:request domain="default"

    xmlns:dp="http://www.datapower.com/schemas/management">

    <dp:get-status class="CPUUsage"/>

    </dp:request>

    </env:Body>

    </env:Envelope>

    Curl command

    curl -k -u user:password -d @soma_getstatus.xml https://DataPowerIP:Port/service/mgmt/current

    Response

    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">

    <env:Body>

    <dp:response xmlns:dp="http://www.datapower.com/schemas/management">

    <dp:timestamp>2008-03-19T17:32:17+01:00</dp:timestamp>

    <dp:status>

    <CPUUsage xmlns:env="http://www.w3.org/2003/05/soap-envelope">

    <tenSeconds>5</tenSeconds>

    <oneMinute>3</oneMinute>

    <tenMinutes>6</tenMinutes>

    <oneHour>6</oneHour>

    <oneDay>6</oneDay>

    </CPUUsage>

    </dp:status>

    </dp:response>

    </env:Body>

    </env:Envelope>

  37. Anonymous (login to see details)

    Chuck,

    we upgraded our dynatrace to 6.3 untill then the plugin was working fine and it stopped after that.  i do see 6.3 is not in the supported env list.

    when can we expect an updated plugin that runs on dynatrace 6.3

     

    Thanks

    Ajay

    1. Anonymous (login to see details)

      Ajay,

      Can you please grab the Collector logs from which the DataPower plugin is executing?  I need to see the details on why it isn't working.  It should work fine with 6.3.

      Thanks!


      Chuck

      1. Anonymous (login to see details)

        Exception is as follows:

         

        2016-08-13 00:48:09 WARNING [UserPluginManager] java.lang.NullPointerException - null

        java.lang.NullPointerException

            at com.dynatrace.diagnostics.sdk.plugins.logging.CompressingFileHandler.publish(SourceFile:40)

            at com.dynatrace.diagnostics.sdk.plugins.logging.DelegationHandler.publish(SourceFile:115)

            at com.dynatrace.diagnostics.util.modern.LogManager$ContextLogger.log(LogManager.java:220)

            at java.util.logging.Logger.doLog(Logger.java:765)

            at java.util.logging.Logger.log(Logger.java:875)

            at DataPower.DataPowerMonitor.callDPSOMAMethod(DataPowerMonitor.java:2989)

            at DataPower.DataPowerMonitor.executeConnectionsAccepted(DataPowerMonitor.java:873)

            at DataPower.DataPowerMonitor.execute(DataPowerMonitor.java:548)

            at com.dynatrace.diagnostics.sdk.UserPluginManager.a(SourceFile:720)

            at com.dynatrace.diagnostics.sdk.UserPluginManager.b(SourceFile:478)

            at com.dynatrace.diagnostics.sdk.UserPluginManager.executePlugin(SourceFile:278)

            at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:50)

            at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:26)

            at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.a(SourceFile:190)

            at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.a(SourceFile:413)

            at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.execute(SourceFile:337)

            at com.dynatrace.diagnostics.schedule.SchedulerJob.a(SourceFile:101)

            at com.dynatrace.diagnostics.schedule.SchedulerJob.work(SourceFile:92)

            at com.dynatrace.diagnostics.schedule.SchedulerJob.executeJobInfo(SourceFile:241)

            at com.dynatrace.diagnostics.schedule.QuartzJob.execute(SourceFile:45)

            at org.quartz.core.JobRunShell.run(JobRunShell.java:202)

            at com.dynatrace.diagnostics.schedule.QuartzThreadPool$WorkerThread.run(SourceFile:788)

  38. Anonymous (login to see details)

    Hi Chuck,

    Are there any plans to add measures for the "dpStatusOtherSensorsTable" group to the plugin?

    Thanks,

    Jake

    CC Charles Miller

  39. Anonymous (login to see details)

    Jake,

    Happy to look at incorporating "dpStatusOtherSensorsTable".  What I ask for in these cases is an example of the SOMA request/response that matches that class.  

    You can do that with curl like the example below replacing CPUUsage with dpStatusOtherSensorsTable (I think).  Also make sure the domain references the domain you care about.

    Thanks!

    Chuck

     

    Request (embed this XML into soma_getstatus.xml and reference like below)

    <?xml version="1.0" encoding="UTF-8"?>

    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">

    <env:Body>

    <dp:request domain="default"

    xmlns:dp="http://www.datapower.com/schemas/management">

    <dp:get-status class="CPUUsage"/>

    </dp:request>

    </env:Body>

    </env:Envelope>

    Curl command

    curl -k -u user:password -d @soma_getstatus.xml https://DataPowerIP:Port/service/mgmt/current

    Response

    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">

    <env:Body>

    <dp:response xmlns:dp="http://www.datapower.com/schemas/management">

    <dp:timestamp>2008-03-19T17:32:17+01:00</dp:timestamp>

    <dp:status>

    <CPUUsage xmlns:env="http://www.w3.org/2003/05/soap-envelope">

    <tenSeconds>5</tenSeconds>

    <oneMinute>3</oneMinute>

    <tenMinutes>6</tenMinutes>

    <oneHour>6</oneHour>

    <oneDay>6</oneDay>

    </CPUUsage>

    </dp:status>

    </dp:response>

    </env:Body>

    </env:Envelope>

  40. Anonymous (login to see details)

    Does the plugin support Dynatrace version 6.5 and Data Power firmware version 7.5.x.x?

     

    1. Anonymous (login to see details)

      John,

      The DP Plugin should now be agnostic to the the DP firmware version.  And it has been tested with 6.5.  Let us know if you have any trouble.

      Thanks!

      Chuck 

  41. Anonymous (login to see details)

    Hi,

    Has anyone tested this plugin in AppMon 7.0 EAP?

    Thanks!

    Kodai

  42. Anonymous (login to see details)

    Kodai,

    I have not explicitly tested it with v7, but I have tested other plugins without any modifications.  There are no changes to the plugin framework so it should work fine.  Please let me know if you have any problems with it.

    Thanks!

    Chuck 

    1. Anonymous (login to see details)

      Hi Chuck,

      Thank you for the response! I will be working on testing this in my local environment today, I will report back if I run into any issues.

      Thanks!

       Kodai

  43. Anonymous (login to see details)

    Running into an issue...

    • Connecting to DP - SUCCESS
    • Authenticating with DP - SUCCESS
    • Sending HTTPS SOAP request to DP - SUCCESS
    • Receiving response from DP - FAILED

    The DP device is returning a response body with an HTTP 500 Internal Server error.

    2017-05-01 16:59:28 FINE [content@New DataPower Monitor_0] << "    </style></head><body><h1>Error 500: Internal Error</h1><p>An internal error has occurred.</p></body></html>"

    Plugin version is 6.2.0.9103

    curl -k -u user:password -d @soma_getstatus.xml https://XX.XX.XX.XX:9090/service/mgmt/current

    </style></head><body><h1>Error 500: Internal Error</h1><p>An internal error has occurred.</p></body></html>

     

     

    1. Anonymous (login to see details)

      The issue was with the configuration of the DataPower device.  The default interface had been changed so much that it did not accept our monitor request.  A new xml interface was added by the administrator and the monitor works as expected.

  44. Anonymous (login to see details)

    Would it be possible to do one call into a DataPower device to query 6 different domains on the one device, but be able to represent the metrics for each domain seperately?  It appears that this is not possible currently and that you can either do the default domain which captures all DP domains in an aggregate manner or you can query each domain on the device separately but that would be 6 calls and not 1 call.  If not currently possible, could the plugin be modified to accomplish the above (1 call which has each domain represented separately).  Thanks.

  45. Anonymous (login to see details)

    Hi,

    We are getting "No appropriate protocol" error while connecting to our Datapower test boxes. Here is the log at FINER level. Can you please help us resolving this?

     

    2017-05-08 15:40:16 INFO [DataPowerMonitor@DataPower Monitor -- Test_0] Executing DataPowerMonitor version 6.2.0.9103 ...nmdptestmgt2.nmg ->https://nmdptestmgt2.nmg:5550/service/mgmt/current
    2017-05-08 15:40:16 INFO [DataPowerMonitor@DataPower Monitor -- Test_0] *******************************************************************1
    2017-05-08 15:40:16 INFO [DataPowerMonitor@DataPower Monitor -- Test_0] *******************************************************************2
    2017-05-08 15:40:16 INFO [DataPowerMonitor@DataPower Monitor -- Test_0] *******************************************************************3
    2017-05-08 15:40:16 INFO [DataPowerMonitor@DataPower Monitor -- Test_0] Populating Connections Accepted Measures for nmdptestmgt2.nmg ->https://nmdptestmgt2.nmg:5550/service/mgmt/current
    2017-05-08 15:40:16 FINE [DataPowerMonitor@DataPower Monitor -- Test_0] auth string: XXXX:XXXXXXX
    2017-05-08 15:40:16 FINE [DataPowerMonitor@DataPower Monitor -- Test_0] Base64 encoded auth string: YWRtaW46RnN0YXJAMTM=
    2017-05-08 15:40:16 WARNING [DataPowerMonitor@DataPower Monitor -- Test_0] Previous message was repeated 3 times.
    2017-05-08 15:40:16 WARNING [DataPowerMonitor@DataPower Monitor -- Test_0] Parsing httpVersion failed, using default: HTTP/1.1
    2017-05-08 15:40:16 FINE [DefaultHttpParams@DataPower Monitor -- Test_0] Set parameter http.protocol.version = HTTP/1.1
    2017-05-08 15:40:16 FINE [DefaultHttpParams@DataPower Monitor -- Test_0] Set parameter http.protocol.max-redirects = 0
    2017-05-08 15:40:16 FINE [DefaultHttpParams@DataPower Monitor -- Test_0] Set parameter http.method.retry-handler = DataPower.DataPowerMonitor$1@7c10acc3
    2017-05-08 15:40:16 INFO [DataPowerMonitor@DataPower Monitor -- Test_0] Executing method: POST, URI: https://nmdptestmgt2.nmg:5550/service/mgmt/current, SOAP Envelope: <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:request domain="AFA_domain" xmlns:dp="http://www.datapower.com/schemas/management"><dp:get-status class="ConnectionsAccepted"/></dp:request></env:Body></env:Envelope>
    2017-05-08 15:40:16 FINE [HttpConnection@DataPower Monitor -- Test_0] Previous message was repeated 3 times.
    2017-05-08 15:40:16 FINE [HttpConnection@DataPower Monitor -- Test_0] Open connection to nmdptestmgt2.nmg:5550
    2017-05-08 15:40:16 FINE [HttpConnection@DataPower Monitor -- Test_1] Previous message was repeated 4 times.
    2017-05-08 15:40:16 FINE [HttpConnection@DataPower Monitor -- Test_1] Open connection to nmdptestmgt1.nmg:5550
    2017-05-08 15:40:16 FINE [header@DataPower Monitor -- Test_0] >> "POST /service/mgmt/current HTTP/1.1[\r][\n]"
    2017-05-08 15:40:16 FINE [HttpMethodBase@DataPower Monitor -- Test_0] Previous message was repeated 3 times.
    2017-05-08 15:40:16 FINE [HttpMethodBase@DataPower Monitor -- Test_0] Adding Host request header
    2017-05-08 15:40:16 FINE [header@DataPower Monitor -- Test_0] >> "Authorization: Basic YWRtaW46RnN0YXJAMTM=[\r][\n]"
    2017-05-08 15:40:16 FINE [header@DataPower Monitor -- Test_0] Previous message was repeated 1 times.
    2017-05-08 15:40:16 FINE [header@DataPower Monitor -- Test_0] >> "User-Agent: Jakarta Commons-HttpClient/3.0.1[\r][\n]"
    2017-05-08 15:40:16 FINE [header@DataPower Monitor -- Test_0] >> "Host: nmdptestmgt2.nmg[\r][\n]"
    2017-05-08 15:40:16 FINE [header@DataPower Monitor -- Test_0] >> "Content-Length: 286[\r][\n]"
    2017-05-08 15:40:16 FINE [header@DataPower Monitor -- Test_0] >> "Content-Type: application/soap+xml; charset=UTF-8[\r][\n]"
    2017-05-08 15:40:16 FINE [header@DataPower Monitor -- Test_0] >> "[\r][\n]"
    2017-05-08 15:40:16 FINE [content@DataPower Monitor -- Test_0] Previous message was repeated 1 times.
    2017-05-08 15:40:16 FINE [content@DataPower Monitor -- Test_0] >> "<?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dp:request domain="AFA_domain" xmlns:dp="http://www.datapower.com/schemas/management"><dp:get-status class="ConnectionsAccepted"/></dp:request></env:Body></env:Envelope>"
    2017-05-08 15:40:16 SEVERE [DataPowerMonitor@DataPower Monitor -- Test_0] null: No appropriate protocol
    2017-05-08 15:40:16 WARNING [UserPluginManager@DataPower Monitor -- Test_0] Previous message was repeated 2 times.
    2017-05-08 15:40:16 WARNING [UserPluginManager@DataPower Monitor -- Test_0] java.lang.NullPointerException - null
    java.lang.NullPointerException
    at com.dynatrace.diagnostics.sdk.plugins.logging.CompressingFileHandler.publish(SourceFile:40)
    at com.dynatrace.diagnostics.sdk.plugins.logging.DelegationHandler.publish(SourceFile:115)
    at com.dynatrace.diagnostics.util.modern.LogManager$ContextLogger.log(LogManager.java:254)
    at java.util.logging.Logger.doLog(Logger.java:642)
    at java.util.logging.Logger.log(Logger.java:731)
    at DataPower.DataPowerMonitor.callDPSOMAMethod(DataPowerMonitor.java:2989)
    at DataPower.DataPowerMonitor.executeConnectionsAccepted(DataPowerMonitor.java:873)
    at DataPower.DataPowerMonitor.execute(DataPowerMonitor.java:548)
    at com.dynatrace.diagnostics.sdk.UserPluginManager.a(SourceFile:713)
    at com.dynatrace.diagnostics.sdk.UserPluginManager.b(SourceFile:476)
    at com.dynatrace.diagnostics.sdk.UserPluginManager.executePlugin(SourceFile:274)
    at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:50)
    at com.dynatrace.diagnostics.sdk.MonitorPluginExecutor.execute(SourceFile:26)
    at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.a(SourceFile:190)
    at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.a(SourceFile:413)
    at com.dynatrace.diagnostics.schedule.ServerJobCenterRegistry.execute(SourceFile:337)
    at com.dynatrace.diagnostics.schedule.SchedulerJob.a(SourceFile:101)
    at com.dynatrace.diagnostics.schedule.SchedulerJob.work(SourceFile:92)
    at com.dynatrace.diagnostics.schedule.SchedulerJob.executeJobInfo(SourceFile:241)
    at com.dynatrace.diagnostics.schedule.QuartzJob.execute(SourceFile:45)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
    at com.dynatrace.diagnostics.schedule.QuartzThreadPool$WorkerThread.run(SourceFile:788)

     

  46. Anonymous (login to see details)

    When the DataPower device goes offline, the HostReachable Measure does not return 0.  Instead, there's no value for the Measure.  Since there's no value for the Measure, we are unable to alert on it crossing the threshold.

    2017-06-19 12:12:45 SEVERE [DataPowerMonitor@Data Power monitor Memory only_3] Previous message was repeated 135 times.
    2017-06-19 12:12:45 SEVERE [DataPowerMonitor@Data Power monitor Memory only_3] Setting response code to 503 due to IOException: : Connection refused
    2017-06-19 12:12:46 SEVERE [DataPowerMonitor@Data Power monitor_3] Previous message was repeated 135 times.
    2017-06-19 12:12:46 SEVERE [DataPowerMonitor@Data Power monitor_3] Setting response code to 503 due to IOException: : Connection refused

    Is anyone else experiencing this?  Is this something that can be changed/fixed in the plugin?