IBM Datapower

DataPower gateways provide mission-critical service/application integration, security, and control. For these devices, Dynatrace offers remote monitoring through the DataPower ActiveGate extension. By ingesting key device data, the extension provides Dynatrace with real-time insight into device health and performance.

Now available in Extensions Framework 2.0, click on Add to environment to get started.

Requirements

• Dynatrace version 1.269+
• ActiveGate version 1.269+
• ActiveGate with the Extensions 2.0 module enabled.
• IBM Datapower appliance with the XML Management Interface enabled.
• User with access permissions to the XML Management Interface.
• Make sure that statistics are enabled in your DataPower instance. Some metrics will be missing if statistics are turned off.

Dynatrace configuration

Under Extensions on the left menu, select IBM Datapower.

• Add a monitoring configuration.

This is an ActiveGate extension and runs on an ActiveGate of an ActiveGate group of your choice.

• XML Management Interface URL: Endpoint where the IBM Datapower XML Management Interface is exposed. Should look something like https://<hostname>:<port>/service/mgmt/current

• User: Used to authenticate against the XML Management Interface. Must have permissions to query it.

• Password: Password to user above.

• Require a valid SSL certificate: If enabled, the extension will use a secure SSL connection to connect to the XML Management Interface. A valid certicate has to be defined in the parameter below.

• Path to a CA_BUNDLE file or directory: If SSL connection is enabled, the absolute path to the SSL certificate to be used.

• Monitoring rules: In this section, you can define rules to monitor or stop monitoring the different Datapower entities.

  • Include all entities: If enabled, it will just monitor all entities of this type. If disabled, and no rules are added, no entities will be monitored.
  • Monitoring rule: Defines a rule to either monitor or ignore an entity. Rules are evaluated in order.
    • Condition: Evaluation condition for the pattern.
    • Pattern: Substring used to match the condition above. It does not accept regex.

• Debug: Produces more verbose logs. Enable only when troubleshooting or support makes that recommendation.

• Lastly, select which feature sets (metric groups) you would like this configuration to collect. Selecting too few will not give you the proper visibility and you may miss out on important performance data, as well as key indicators that can be correlated between different objects.

Alerting

The extension comes wtih 10 built-in metric events for the most relevant Datapower metrics and their thresholds. These metric events are disabled by default, but you can navigate over to Settings, Anomaly Detection and Metric events to enable them. These 10 metrics events are:

• Connectivity lost: Alert when connectivity is below 100% for a Datapower instance.
• Crypto Engine failure: Alert when the crypto engine availability is below 100%.
• Network receive errors: Alert when an interface has at least 1 network receive error.
• Network transmit errors: Alert when an interface has at least 1 network transmit error.
• High CPU load: Alert when CPU load is above 95% for a Datapower instance.
• Critical load: Alert when a Datapower instance's load is bove 90%.
• Critical memory utilization: Alert when memory load of a Datapower instance is above 60%.
• Records lost: Alert when amount of records lost is at least 1.
• Pending messages queue: Alert when the pending messages count is above 3000.
• Service is down: Alert when a Datapower service's status is down.