Monitoring Apache ActiveMQ
Learn how to monitor all your Apache ActiveMQ services and queues according to user-defined thresholds.
This agent allows you to monitor ActiveMQ queues. Checks can be performed on the allowed number of messages within them. Also, the maximum age of the first message on the queue can be verified. You decide in the configuration file which server and queue it is you want to monitor, as well as the number of messages on which Nodinite should warn/fail for.
Stockpiling messages is terrible for your business. So we developed this Monitoring Agent to give end-users the power to get alerts and manage content to keep the system healthy.
This section describes what's being monitored and the rules for how Nodinite translates this into meaningful monitoring states. Also, some remote commands are available as Actions to help you swiftly manage problems. Actions are further detailed on the Managing ActiveMQ page.
List of ActiveMQ resources in a Nodinite Monitor View.
Monitoring Features
- Automatic Discovery
- The Nodinite Message Queueing Monitoring Agent offers the automatic discovery of queues on the configured ActiveMQ Servers. Sharing access to any individual queue is very easy from within Nodinite using Monitor Views.
- State Evaluation - Make sure the Broker is operational and Queues are not stockpiling
- Age and count - Provides means to get you alerted if queues are stockpiling messages.
If Nodinite can't check the state of your queues, chances are no one else can use them either.
- Age and count - Provides means to get you alerted if queues are stockpiling messages.
- Category-based monitoring - To help you sort out the different type of ActiveMQ artifacts the monitored Resources are grouped by Categories
List of categories in the Monitoring.
State evaluation
Each monitored 'Service Bus Queue' is displayed in Monitor Views within Nodinite as one Resource with its currently evaluated state. If you have 42 deployed Azure Service Bus, then you will have 42 Resources in Nodinite with potentially different monitored evaluated states at any given moment.
Live overview with different states summarized in a pie chart.
The evaluated state may be reconfigured using the Expected State override setting on every Resource within Nodinite.
ActiveMQ Broker
One ActiveMQ Broker is displayed within Nodinite as one Resource. If you have 3 ActiveMQ Brokers, then you will have 3 Resources in Nodinite.
- All Apache ActiveMQ Services belong to the 'ActiveMQ Broker' category:
- The Application name is based on the display name from the Configuration
- The Resource name is the same as the Application name
Here's an example of Monitor View filtered by category 'ActiveMQ Broker'
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available | Evaluation of the 'ActiveMQ Broker' is not possible either due to network or security-related problems | Review prerequisites | |
| OK | ActiveMQ Broker is online | No problems exists connecting with the ActiveMQ broker | N/A |
From within Nodinite, you can reconfigure the state evaluation on Resource level using the Expected State feature.
ActiveMQ Queue
- All ActiveMQ queues belong to the 'ActiveMQ Queue' category:
- The Application name is based on the display name from the Configuration This pattern guarantees uniqueness and a queue with the same name on different ActiveMQ brokers can be distinguished.
- The Resource name is the name of the queue.
Each monitored Service Bus Queue is a Resource and can have one of the following states at any given moment:
List of resources of category 'ActiveMQ - Queues' in a Monitor View
Queue evaluations
The Nodinite Message Queueing Monitoring Agent evaluates the age and number of messages on queues. There will be one Resource for each queue available within Monitor Views (where included).
Whenever a queue has too many (or too old) messages, the Resource is evaluated as being in state Error or Warning depending on user-defined thresholds. It will remain in this state until the error condition is cleared by either removing messages or managing thresholds.
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available | Evaluation of the 'ActiveMQ Queue' is not possible either due to network or security-related problems | Review prerequisites | |
| Error | Error threshold is breached | Queue has too many or too old messages according to user-defined thresholds | Edit thresholds List messages | |
| Warning | Warning threshold is breached | Queue has too many or too old messages according to user-defined thresholds | Edit thresholds List messages | |
| OK | Within user-defined thresholds | Queue has NO not too many or too old messages according to user-defined thresholds | Edit thresholds List messages |
From within Nodinite, you can reconfigure the state evaluation on Resource level using the Expected State feature.
Alert history
During root cause analysis or other purposes, it might be helpful to understand how often your Queues problems happen. If your Monitor View allows it, you can search for historical state changes for the provided time span, either for all your queues and ActiveMQ services or individually. This topic is further detailed within the generic instructions on how to Add or manage Monitor View page.
| Search | Resource history |
|---|---|
 Search for alert history for all resources in the Monitor View |
 Alert history for the selected queue |
Frequently asked questions
Use the troubleshooting guide to find the FAQ and answers to known problems.