WSO2 API Manager extension

• Latest Dynatrace
• Extension
• Updated on Jun 15, 2026

Gain insights into your WSO2 deployment.

Monitor WSO2 specific metrics for your OneAgent monitored processes.

Get started

Overview

This extension retrieves metrics through the JMX framework, using the default MBeans exposed by WSO2 API Manager. For more information, see the JMX-Based Monitoring documentation.

Use cases

Use this extension to:

Requirements

Compatibility information

This extension supports the following versions of the WSO2 API Manager:

Details

Licensing and costs

There is no charge to use the extension. You are only charged for the data that the extension ingests.

The WSO2 API Manager extension ingests custom metrics, which consume Davis Data Units (DDUs) (Dynatrace classic license) or Metrics powered by Grail (DPS), according to your license model.

In total, the WSO2 API Manager extension collects 27 metrics per process group instance per minute. You can estimate the metric data points produced per minute by using the following formula:

27 * N

N represents the number of process group instances reporting metrics to this extension.

Dynatrace Platform Subscription

In the Dynatrace Platform Subscription, metric ingestion consumes Metrics powered by Grail according to the number of ingested metric data points.

To calculate the approximate yearly consumption, apply the following calculation: <metric data points per minute> * 60 minutes * 24 hours * 365 days.

Dynatrace classic license

In the classic licensing model, metric ingestion consumes Davis Data Units (DDUs) at the rate of .001 DDUs per metric data point. Multiply the above formula for annual data points by .001 to estimate annual DDU usage.

The DDU cost above does not include any possible log events or custom events that are triggered by the extension. For more information, see DDU events.

FAQ

If you don't see any metrics, or are missing some metrics, ensure that your deployment exposes MBeans in the following namespaces:

Using a tool like jConsole can be useful in these situations.

Feature sets

When activating your extension using a monitoring configuration, you can limit monitoring to one of the feature sets. To work properly, the extension has to collect at least one metric after the activation.

In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.

All metrics that aren't categorized into any feature set are considered to be the default and are always reported.

Explore in Dynatrace Hub

Gain insights into your WSO2 deployment.