Wanted to run this by the community for some advice. We have 20 brokers in total (10 master/slave pairs). Operational tooling is an issue, we need something simple to address short term needs. So our goal is to create a web page showing unified operational view for the entire cluster. Simple metrics for each broker (master/slave role, process load, memory, connections, store/temp usage), is all we need for now. Each broker
Our first thought was to create a JMX spring service configured to run inside the broker. The service opens a local JMX connection, polls the desired metrics, and publishes to "topic/metrics" on the local broker as a simple json payload. The problem with this approach is it doesn't work when the broker is a slave. An alternative option is along the same lines, a JMX service running inside the broker, but the difference is that, on startup, the services creates an embedded broker with single network connector configured to talk to all other brokers in the cluster. Now, regardless of the broker's role, "topic/metrics" is always a valid topic for publishing and consuming metrics info for the entire cluster. Another option is using advisory messages for carrying metrics info, although we're not sure if flooding this channel with such data will negatively impact openwire clients receiving cluster updates with no interest in metrics. -- View this message in context: http://activemq.2283324.n4.nabble.com/Using-topics-for-publishing-broker-metrics-tp4705077.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
