After applying JMX filtering pattern, it takes 23 secs to scrape the metrics, is it expected behaviour? about jmx_exporter HOT 6 CLOSED

@sreelu27 The exporter metrics response time is a function of your exporter rules and the Kafka MBeans execution time.

Your only options are to change your exporter rules or increase your Prometheus (calling code) scrape interval.

from jmx_exporter.

@sreelu27 the Kafka MBean execution time is causing the slow scrape time. The Kafka project would have to increase MBean performance.

We can't solve this in the exporter code.

from jmx_exporter.

Thank you @dhoard for the quick response. Will definitely try the suggestion.

from jmx_exporter.

Hi @dhoard,

After testing with minimal patterns with minimal filtering, we are getting better scrape time.

I have a query in future if we add more patterns again scrape time may increase, even in the minimal pattern if we add more filtering will also leading the scrape timeout issue.

So, Could you please share if you have any plans in future to handle this scenario/use case?

Thanks,
Sree

from jmx_exporter.

Thank you for your response. Much appreciated @dhoard

from jmx_exporter.

Closing as resolved.

from jmx_exporter.