Github user ted-ross commented on the issue:
https://github.com/apache/qpid-dispatch/pull/159
I share Chuck's concern that this PR is introducing an alternative and
redundant management access mechanism. I would certainly prefer to add the
desired metrics to the AMQP-based access mechanism that is already in place.
One of the advantages of the AMQP management mechanism is that it is
routable. With a single connection to a router in a network, a process can
query data from all of the routers in the network (and eventually brokers as
well). Using the HTTP access point only allows access to a single router.
Is there a way to bridge the gap between the AMQP management protocol and
Prometheus?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
