topic Re: After moving to DPS, How to break down DPS metric consumption by extension? in Dynatrace Managed Q&A

After moving to DPS, How to break down DPS metric consumption by extension?

Yos_Neu-Poalim — Mon, 13 Jul 2026 06:19:12 GMT

Hi guys,

In the classic licensing model, we used the DDU consumption menu to easily understand how much licensing volume

each extension was costing us.

Since moving to DPS, this menu has disappeared.

We tried using the following metric to get a breakdown:
builtin:billing.custom_metrics_classic.usage.other_by_entity:splitBy("dt.entity.monitored_entity")

However, the monitored_entity dimension simply displays the global environment name rather than splitting the usage by individual extension names.

Next, we tried using this raw metric:
builtin:billing.custom_metrics_classic.raw.usage_by_metric_key:splitBy("metric_key")

While this gives us the individual metric keys, the classic query engine in Dynatrace Managed does not provide a way to manipulate strings or group the data. We cannot find a way to sum the data points by their metric prefix (e.g., ibmmq.*, kafka_*, remote.*, db2.*) to see the total consumption per extension.

Has anyone found a way to nativey display or chart this information within the Managed UI without exporting the data externally?

Thanks in advance for your insight

@ezra_zilcha & Yos

Re: After moving to DPS, How to break down DPS metric consumption by extension?

AntonPineiro — Mon, 13 Jul 2026 07:46:01 GMT

Hi,

It has a direct relation to how many data point are being ingested. Maybe you can check this DQL query:

fetch metric.series | filter matchesPhrase(metric.key, "XXXX") | summarize count = count(), by:{metric.key} | sort count desc

Filter is optional, it is just in case you want to filter by "extension".

Best regards

Re: After moving to DPS, How to break down DPS metric consumption by extension?

Yos_Neu-Poalim — Mon, 13 Jul 2026 09:46:50 GMT

Hi @AntonPineiro

Unfortunately this is still a Managed environment without DQL capability to query the data.

Thanks

Yos

Re: After moving to DPS, How to break down DPS metric consumption by extension?

AntonPineiro — Mon, 13 Jul 2026 10:05:05 GMT

Hi,

Do you have DPS using Managed? It is strange...

Best regards

Re: After moving to DPS, How to break down DPS metric consumption by extension?

Yos_Neu-Poalim — Mon, 13 Jul 2026 10:43:04 GMT

Yes its managed using DPS license AKA DPS for Hybrid

HTH

Yos

Re: After moving to DPS, How to break down DPS metric consumption by extension?

Kenny_Gillette — Mon, 13 Jul 2026 19:11:16 GMT

Talk with your account team? cc Sophie_Mayerw

Re: After moving to DPS, How to break down DPS metric consumption by extension?

dylan_taelemans — Tue, 14 Jul 2026 10:23:13 GMT

Hey,

I have a couple of those hybrid customers as well. (Not a recommendation, as it has issues)
Not possible natively (so not a true solution) ,but I use the following approach in these kind of cases:

You can use the following Data Explorer query:
builtin:billing.custom_metrics_classic.raw.usage_by_metric_key:splitBy(metric_key):names:sort(dimension(metric_key,descending))

Export the results as CSV and then either:

Use a custom Python script to categorize the metrics, or
Take the easier route and upload the CSV to an AI tool like Gemini or ChatGPT to help categorize them.

If you use AI, make sure to validate the results yourself, as the categorization may not always be 100% accurate. (Sometimes it takes 2–3 attempts to get the results perfect.)

Here is an example of the output:

After AI processing:

If you really want to keep it entirely within Dynatrace, you could create a custom extension that fetches the data through the Dynatrace API, uses Python logic to calculate the datapoints per extension, and then sends the results back into Dynatrace as a new metric.

I have considered this approach before, but it feels like a workaround for something that should be much simpler. It would also require quite a bit of ongoing maintenance, which makes it even less appealing.