Monitoring MuleSoft AnypointMQ
Stockpiling messages can be detrimental to your business. To address this issue, we developed the Nodinite Monitoring Agent, which empowers end-users to receive alerts and manage content effectively, ensuring the system remains healthy.
This agent enables you to monitor AnypointMQ queues. You can perform checks on the maximum allowed number of messages in the queues, as well as verify the maximum age of the first message on each queue.
This section outlines what is being monitored and explains how Nodinite interprets this information into meaningful monitoring states. Additionally, some remote commands are available as Remote Actions to help you quickly address any problems. For more details on these actions, please refer to the Managing AnypointMQ page.
Here is a list of AnypointMQ Resources in a Nodinite Monitor View.
Monitoring Features
Automatic Discovery - The Nodinite Message Queueing Monitoring Agent automatically detects queues on the configured AnypointMQ servers. Sharing access to any individual queue is straightforward through Nodinite using one or more role-based Monitor Views.
State Evaluation - Ensure the AnypointMQ service is operational and that queues are not accumulating an excessive number of messages.
- Age: Receive alerts when message stockpiling may lead to performance issues.
- Count: Get notified when messages in queues are not being processed.
- Service Status: Get notifications when the AnypointMQ service is not operational.
Note
If Nodinite cannot check the state of your AnypointMQ queues and services, it is likely that no one else can use them effectively either.
- Category-Based Monitoring - To help differentiate between various types of AnypointMQ artifacts, monitored Resources are grouped into categories. The AnypointMQ-related artifacts are categorized as follows:
- AnypointMQ Broker: The broker service itself
- AnypointMQ Queue
Here's an example with a list of diffferent AnypointMQ related Monitoring Categories.
State evaluation
The Nodinite Message Queueing Monitoring Agent includes a variety of monitoring features related to AnypointMQ that utilize either global or specific settings to assess the age and number of messages across different queue types. Each queue has a corresponding Resource with an evaluated state, which you can incorporate into one or more Nodinite Monitor Views as you wish.
Live overview with different states summarized in a pie chart.
From within Nodinite, you can reconfigure the state evaluation on Resource level using the Expected State feature.
AnypointMQ Broker
For instance, if you have 3 AnypoingMQ Brokers, you will have 3 Resources available for use in one or more Monitor Views, each potentially reflecting different evaluated states at any given time.
- All MuleSoft AnypointMQ Services belong to the 'AnypointMQ 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 'AnypointMQ Broker'
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available | Evaluation of the 'AnypointMQ Broker' is not possible either due to network or security-related problems | Review prerequisites | |
| OK | AnypointMQ Broker is online | No problems exists connecting with the AnypointMQ broker | N/A |
AnypointMQ Queue
- All AnypointMQ queues belong to the 'AnypointMQ 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 AnypointMQ 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 'AnypointMQ - Queues' in a Nodinite self-service Monitor View.
Queue evaluations
When a queue contains too many messages or messages that are too old, its Resource is evaluated as being in an Error or Warning state, depending on thresholds defined by the user. This state will persist until the error condition is resolved, either by processing/removing messages or adjusting the thresholds.
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available | Evaluation of the 'AnypointMQ 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 | |
| Warning | Warning threshold is breached | Queue has too many or too old messages according to user-defined thresholds | Edit thresholds | |
| OK | Within user-defined thresholds | Queue has NO not too many or too old messages according to user-defined thresholds | Edit thresholds |
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 AnypointMQ 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 AnypointMQ 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.