You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if the jolokia plugin would pull JMX data via the jolokia bulk request https://jolokia.org/features/bulk-requests.html mechanism in order to reduce round trips to the JVM.
Current behavior:
Jolokia plugin makes one HTTP request for every mbean.
Desired behavior:
One request per JVM
Use case:
With lots of JMX data collected per JVM, telegraph will need to machine gun the JVMs as it collects all of the stats. Each mbean translates into a separate HTTP requests. With bulk requests, the multiple HTTP requests could be reduced to one.
The text was updated successfully, but these errors were encountered:
PR is up for this over at #2253
In my use case it's about 260 times faster. Though to be fair, there's probably some accuracy errors in the math because the new timings are so fast (0.04s vs 10.4s).
Proposal:
It would be great if the jolokia plugin would pull JMX data via the jolokia bulk request https://jolokia.org/features/bulk-requests.html mechanism in order to reduce round trips to the JVM.
Current behavior:
Jolokia plugin makes one HTTP request for every mbean.
Desired behavior:
One request per JVM
Use case:
With lots of JMX data collected per JVM, telegraph will need to machine gun the JVMs as it collects all of the stats. Each mbean translates into a separate HTTP requests. With bulk requests, the multiple HTTP requests could be reduced to one.
The text was updated successfully, but these errors were encountered: