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
I would suggest to only add new supported systems directly in instrumentation as we can now reuse them directly with jmx-scraper thanks to open-telemetry/opentelemetry-java-contrib#1782.
However, most of the code to test new systems is in #13392 which is not merged yet due to lack of ability to filter negative values.
In practice this does not prevent starting the fun part which is to create a yaml file and define metrics by putting it in the right location in classpath (see tests in open-telemetry/opentelemetry-java-contrib#1782).
Thanks @SylvainJuge you make a good point about adding to instrumentation first. What do you think about us moving this issue then over to the instrumentation repo?
Yes, moving the issue to instrumentation would make sense here. It's probably a good idea to start working on this only once we have merged the JVM metrics PR as it provides the test infrastructure.
trask
transferred this issue from open-telemetry/opentelemetry-java-contrib
Mar 19, 2025
Component(s)
jmx-scraper
Is your feature request related to a problem? Please describe.
Trino publishes a set of JMX metrics: https://trino.io/docs/current/admin/jmx.html
We could incorporate a configuration that would allow users to scrape these with the
jmx-scraper
.Describe the solution you'd like
It would be awesome if the
jmx-scraper
had out-of-the-box support for scraping the Trino metrics. https://trino.io/docs/current/admin/jmx.htmlThe text was updated successfully, but these errors were encountered: