IBM Datapower

NOTE:

• This extension requires ActiveGate version 1.313.0 or later.

New in this version

• Implemented EndpointStatuses.

Improved in this version

• Improved error messaging with DECs.

🚀 Improved in this version:

• Timeout when calling Datapower increased
• Logs are much less verbose now with INFO level for easier troubleshooting

✨ New in this version:

• Add support for the dt.security_context attribute
• DNS resolution to obtain the device.address now runs only after a specific frequency and not every time we push a metric. This frequency can be modified with the new Hostname resolution frequency configuration parameter, which defaults to every 24 hours.

🐛 Fixed in this version:

• Dimensions now properly never go above the limit of 256 characters
• Further parse dimensions to avoid metric rejections based on tab characters
• Fixed overview dashboard referencing an inexistent metric
• urrllib3 library updated to avoid security risk

• Added support for gen3 charts/screens for future compatibility with I&O app

• Adds device.address dimension to all ingested metrics.
• Adds RAID metrics feature set and metrics (Chart can be found in DataPower Instance UA Screen):
  • IBM.DataPower.RAID.totalSize
  • IBM.DataPower.RAID.freeSpace
• Adds Gateway Peering metrics feature set and metrics (Chart can be found in Datapower Domain UA Screen):
  • IBM.DataPower.Gateway.apiRateLimitingPeering
  • IBM.DataPower.Gateway.apiSecurityTokenPeering
• Fixes MQQM metrics for versions 9+.

• Fixed a bug where MQ metrics were not being captured correctly for versions 9 and above of Datapower.
• Fixed a bug where the metric IBM.DataPower.LoadBalancer.adminState was not being linked to any entity.

• Added 3rd gen dashboard

• Fixed a bug where data stopped being ingested for older versions of Datapower

✨ New in this version:

• Added support for MQ Manager metrics for IBM Datapower version 9+.
• Added support for API Gateway service metrics.

🐛 Fixed in this version:

• Fixed a bug where object status metrics were not being captured correctly.

• Fixed issue where username/password fields were still appearing if credential vault toggle was on.

🚀 Improved in this version:

• Increased maximum number of splits per metric from 1000 to unlimited.

✨ New in this version:

• Added support for configuring credentials directly from the credential vault.
• Added 5 new metrics for Web Services, with their relevant generic entity, relationships and chart:
  • IBM.DataPower.WebService.lastResponseTime
  • IBM.DataPower.WebService.failedRequests.count
  • IBM.DataPower.WebService.totalRequests.count
  • IBM.DataPower.WebService.successfulRequests.count
  • IBM.DataPower.WebService.serviceTime.count

🐛 Fixed in this version:

• Properly escape special characters to prevent invalid lines.
• Automatically shrink dimension values to avoid exceeding the limit.

• Fixed a bug where the relationship between a datapower instance and a datapower task was inexistent

• Disabling feature sets now prevents the extension from performing the queries related to the metrics included in said feature sets.

Attention: This version brings breaking changes to existing configurations, meaning you will need to re-create your configurations from scratch when updating them.

New additions:

• A total of 65 metrics split between 9 feature sets
• Charts where relevant for the above metrics
• Topology for MQ Managers and SLM Policies, entities introduced with the new metrics, including their relationships to the rest of the topology
• Configuration parameters for filtering the above entities
• Configuration parameter to accept client certificate configuration
• Configuration parameter bucket size for configuring how many endpoints should run on each - ActiveGate of the selected ActiveGate group for better balancing

• Fixed a bug where metrics were not attached to any entity

• Fix an issue where sometimes the connectivity metric was not pushed correctly

• Fixed a bug where the availability metric was not ingested correctly when Datapower worked with too many IPs

• Fixed a bug where Load Balancer entities where not being generated

• Fixed a bug where MINT lines were too long to be ingested
• Fixed a bug where incorrect timezone/timestamp would prevent metrics from being ingested

• Added option for exclude rules instead of only include.
• Added support for multiple endpoint configuration.
  • This changes the activation schema which will prevent you from updating your older configurations to this new version. You will need to create your configurations from scratch.
• Fixed a bug with topology where entities of different domains were being merged.

Modified the overview dashboard to show interface traffic instead of status, as the status is missing from many datapower installations.

• Added new metric IBM.DataPower.activeTransactions and added graph for it on the DataPower instance screen.
• Extension no longer pushes events but pushes logs instead.
  • This new feature allows you to create your own alerting based on these logs.
  • A new configuration parameter has been included to control log ingestion to either enable or disable it.
    • Because of this new parameter, old configurations of the extension cannot be migrated to this version and instead you have to re-create them from scratch.
• Fixed a bug where non-existing load balancer metrics would crash the entire extension.

• Fixed a bug where interface metrics where never captured

Extension conversion to Extensions Framework 2.0:

• Added custom topology for Datapower entities and their relationships
• Added screens for all the entities
• Added metric metadata
• Added metric events for alerting
• Added out of the box dashboard
• Added feature sets
• Added metrics for interfaces, services, load balancers and admin/oper status of objects
• Replaced regex with Dynatrace-friendly rules
• Removed configuration for client certificate

All metrics ingested by the new extension are prefixed with IBM.DataPower and drop the builtin:tech prefix. Any older configuration such as metric events or dashboards that use the old metric key will need to be replaced with the new one.