Hello everyone, thanks for starting this discussion Hailey. I think having a separate repository is a good idea. It can make the development faster and, like Matt said, avoids bloating the broker with new dependencies. Also, over time when the plugging matures we can bring it into the "main" ActiveMQ repository if we want (I think doing the other way around is harder).
Sérgio Lemos Em sáb., 18 de jul. de 2026 às 06:23, mattrpav (via GitHub) <[email protected]> escreveu: > > GitHub user mattrpav added a comment to the discussion: Prometheus Broker > Plugin for Apache ActiveMQ > > Hi @hai-ben! > > Thanks for kicking off this discussion. I'm a big fan of having modern, > first-class monitoring and reporting integrations. > > Can you link the RabbitMQ plugin? I think it would be helpful to clarify > the target features and scope-- > > 1. Replace the need for the prometheus agent for polled metrics? > > 2. Extend the drafted OpenTelemetry plugin to support collecting tracing > data? > > 3. Both? > > One thing to note-- I'm cautious of adding a bunch of 3rd-party > dependencies to the main repo. ActiveMQ has outlived many trendy monitoring > and alerting platforms. When those get flagged for security, it tends to > flag the whole broker. > > Side quest-- I'm wondering if having an 'extras' or 'third-party' repo for > extensions would be a way to manage this. For example-- activemq-shiro and > activemq-log4j-appender are third-party add-ons that really aren't part of > the broker. > > > > GitHub link: > https://github.com/apache/activemq/discussions/2226#discussioncomment-17681105 > > ---- > This is an automatically sent email for [email protected]. > To unsubscribe, please send an email to: > [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > For further information, visit: https://activemq.apache.org/contact > > >
