Apache ActiveMQ is an open source message broker written in Java with a full JMS client. It provides a multi-protocol message broker that supports a wide range of messaging protocols, including JMS, AMQP, STOMP and MQTT. It is an enterprise-grade message broker that helps to integrate and manage enterprise applications.
The prerequisites for monitoring ActiveMQ with Netdata are to have ActiveMQ and Netdata installed on your system.
Netdata auto discovers hundreds of services, and for those it doesn’t turning on manual discovery is a one line configuration. For more information on configuring Netdata for ActiveMQ monitoring please read the collector documentation.
You should now see the ActiveMQ section on the Overview tab in Netdata Cloud already populated with charts about all the metrics you care about.
Netdata has a public demo space (no login required) where you can explore different monitoring use-cases and get a feel for Netdata.
The number of messages that are being enqueued and dequeued from an ActiveMQ broker. Enqueued messages refer to the number of messages added to the broker’s queue, while dequeued messages refer to the number of messages removed from the queue. It is important to monitor this metric to ensure that the broker is functioning correctly and that messages are being processed in a timely manner. If the number of enqueued messages is significantly higher than the number of dequeued messages, it may indicate that the broker is not processing messages quickly enough, and that message queues are beginning to back up. Monitoring this metric can help to prevent backlogs and ensure that messages are being processed in a timely manner.
The number of messages which were not successfully processed by the ActiveMQ broker. This metric is important to monitor as it can indicate potential issues with the broker, such as an inability to process messages due to lack of resources or configuration errors. If the number of unprocessed messages is high, it may be necessary to investigate the cause and take corrective action.
The number of consumers connected to an ActiveMQ broker. Monitoring this metric can help to identify potential issues with the broker, such as an inability to process messages due to lack of resources or configuration errors. If the number of consumers is too high, it may be necessary to investigate the cause and take corrective action.