Our great sponsors
-
not quite sure if this is where I should be asking for help but i'm kind of befuddled about this whole situation. I'm trying to set up https://github.com/prometheus/jmx_exporter for our containerized Java application on our cluster. Specifically the JavaAgent as we are interested in getting the CPU and memory metrics especially. However, getting it initialized I am faced with this:
-
After doing some research it appears this class references internal packages and therefore "makes it unusable for modern Java apps" (https://github.com/prometheus/client_java/issues/533 , https://github.com/open-telemetry/opentelemetry-java/issues/4192)
-
InfluxDB
Collect and Analyze Billions of Data Points in Real Time. Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge.
-
After doing some research it appears this class references internal packages and therefore "makes it unusable for modern Java apps" (https://github.com/prometheus/client_java/issues/533 , https://github.com/open-telemetry/opentelemetry-java/issues/4192)
-
For CPU and memory metrics, you can use cAdvisor to collect container level data.
-
In case you don’t get it working you could try JMX metrics from OTEL contrib. Configure it for the Prom exporter.
-
Download this package to your container: https://github.com/macagua/example.java.helloworld Compile Main.java and create the jar file according to the instructions. Run the jar file with the jmx exporter with:
Related posts
- OpenTelemetry in 2023
- Show HN: Autometrics Explorer – A Contextual UI for Prometheus
- Initial setup
- autometrics: easily add metrics to any function -- and jump to live Prometheus charts directly from your IDE (links with automatically customized PromQL queries are inserted into each function's doc comments)
- Pod log monitoring