Legacy metric event though EF2

elenaperez — Tue, 28 Jul 2026 08:36:00 GMT

Hi team,

We noticed the following in the Kafka version in use (2.5).
In Dynatrace, the metric is displayed as:
legacy.kafka.kafka.network.RequestMetrics.RequestsPerSec.FetchConsumer.OneMinuteRate.request
However, in the extension documentation, it appears as:
kafka.network.RequestMetrics.RequestsPerSec.FetchConsumer.OneMinuteRate
Could this difference be related to the deprecated Kafka version, or is there another reason why Dynatrace is reporting the metric with the legacy.kafka prefix and the additional .request suffix?

They are using EF2 and the only available metric is the legacy one.

They also don't seem to have any custom EF1 JMX metrics.

Thanks in advance!

Re: Legacy metric event though EF2

sujit_k_singh — Mon, 10 Aug 2026 03:00:11 GMT

Hi @elenaperez

I'm not sure whether this has been resolved yet since this is a bit of an older post, but here is my two cents on the issue:

This behavior is typically not related to Kafka 2.5 being deprecated. When Dynatrace captures JMX MBeans via the legacy JMX plugin framework (EF 1.0) rather than through the new EF 2.0 engine, it prepends legacy. (or legacy.kafka.) to avoid metric key collisions with Extensions 2.0. If EF2 isn't receiving or binding to the expected MBean attributes directly, the backend falls back to reporting the legacy metrics captured by OneAgent.

The .request suffix is appended by OneAgent's legacy JMX metric generator when converting counter attributes or multi-value composite data structures into standalone metric keys.

Thanks,

Sujit

topic Re: Legacy metric event though EF2 in Extensions

Legacy metric event though EF2

Re: Legacy metric event though EF2