-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify in documentation "jvm_*" metrics #964
Comments
@ecerulm we have a subtle statement... "It can be also run as a standalone HTTP server and scrape remote JMX targets, but this has various disadvantages, such as being harder to configure and being unable to expose process metrics (e.g., memory and CPU usage)." What would you propose? The standalone can export JVM metrics, but they will be reported more in line with the actual MBean ObjectNames... Example:
|
I wrote #965 with a specific proposal. My issues is that I tried searching for
And that is perfectly fine, it just that In my case I can't use the javagent because the application I'm trying to monitor (Tableau) does not allow me to add the agent. It comes with it's own tool to start many java services and it does not allow to customize any java options (not supported either). But "regular" JMX is allowed, hence jmxexporter http server is a good fit for me. |
Many (most?) of the JVM metrics are directly accessible from MBeans attributes, yes. The above is just for reference in case somebody lands here looking for FYI, I added some information about |
Added documentation to 1.0.1 README.md |
I thought that the metrics
were "standard" in jmx_exporter but it seems that they are only exported for the javagent and not the httpserver. I don't think this is mentioned in the documentation, I think it would be good to clarify somewhere the discrepancy between javaagent in httpserver.
Just to illustrate my point
httpserver
Running the jmxexporter httpserver give 0
jvm_
metricsjavaagent
On the other hand jmxexporter agent give a 98
jvm_
metricsThe text was updated successfully, but these errors were encountered: