opentelemetry-java VS Centreon

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 monitoring: If you want to go the open source route, the open telemetry ecosystem is booming. You could use the open telemetry java agent along with their collector, and then use Elastic APM, which could give you a good starting point. Here is a small example project I found on github that was fun to play around with and explore the capabilities of a setup like this: https://github.com/riferrei/otel-with-apache-pulsar

OpenTelemetry and Java Flight Recorder (JFR) cover most bases. Use the OpenTelemetry Java agent if you want auto-instrumentation or just the APIs if you want to do your own instrumentation.

opentelemetry-java - contains components for manual instrumentation as well as the API and SDK.

opentelemetry-java This repo is the main OpenTelemetry Java SDK and provides components for manual instrumentation. Top-level components include OpenTelemetry API, extensions, SDK, bridge layers for OpenTracing and OpenCensus.

Understand your organization structure, know what all services are deployed, build a service map and dependencies, understand what all key indicators/metrics are important. Scrape them by python and push them in elastic search and render those metrics in kibana. Monitor all your base machines in Centreon/nagios (https://www.centreon.com).