hai-ben commented on PR #2402: URL: https://github.com/apache/activemq/pull/2402#issuecomment-5701698580
Thanks folks for letting me know the rationale isn't clear. Stepping back, the underlying problem I'm trying to fix is that ActiveMQ exposes MBean attributes but does not provide an out of the box way to map those to make to metrics, which makes each monitoring stack unique deployment specific. @cshannon, the way I see jmx_exporter, is that it provides a way to make and use a mapping of MBean attributes to metrics, but doesn't provide a mapping, so nothing works out of the box. This is the pain point I'm trying to solve, I just see this Prometheus servlet as the easiest path to fixing that problem. I'm committed to maintaining it. @jbonofre and for OTel, it's sort of the same problem, it's a way to expose metrics, but it's mapping agnostic with steps needed to get it running out of the box. So this is complementary, OTel could be set up to scrape and export this endpoint. My goal is to provide end users some batteries included way to get started monitoring their broker right away without needing to have an opinion on MBean attributes. I'm updating the PR to make this off by default with a toggle in the config and cleaning up the example grafana dashboard. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
