More Reporting On Number of Metrics Collected / Work Performed By Agent

[JimHagan]

A customer is running an analysis on the impact of the running nrjmx agent on their environemment and see request duration average creep up when running.

Now the performance team wants to find better ways to know how many metrics are being processed in each run. It's likely they may try to optimize the metric configurations based on these performance metrics.

• Can we configure debug log level and is it likely to show us the number of metrics processed per fetch
• Or can we consider having a rollup report on each run just saying how many metrics are gathered per each fetch per host

I will share two screenshots from the customer's benchmark environment:

WITH nrjmx running

WITHOUT nrjmx running

[josemore]

Thanks for sharing the performance insights @JimHagan
There might be multiple approaches to get more insights. One way might be enabling the trace log level v3.submission which will print all requests made to the backend when pushing NR events. In correlation with verbose logs you should be able to see number of metrics being processed on each execution.

[davidgit]

This issue was closed because it has been inactive for a long time despite it can be reopened at any point if you think it still relevant.

Thank you for your contribution!