Dynatrace ActiveMQ server monitoring provides information about queues, brokers, and more. If ActiveMQ nodes are underperforming or a problem occurs, Dynatrace lets you know immediately and shows you why.
- Linux OS
- ActiveMQ 5.8.0 or higher
- Docker-compatible containers
- Dynatrace OneAgent on all nodes
- JMX monitoring enabled
Enabling ActiveMQ monitoring globally
With ActiveMQ monitoring enabled globally, Dynatrace automatically collects ActiveMQ metrics whenever a new host running ActiveMQ is detected in your environment.
- In the navigation menu, select Settings.
- Select Monitoring > Monitored technologies.
- On the Supported technologies tab, find the ActiveMQ JMX row.
- Set the ActiveMQ JMX switch to the On position.
Monitoring ActiveMQ in Dynatrace
In the navigation menu, select Technologies.
Click the ActiveMQ tile on the Technology overview page.
To view cluster metrics, find ActiveMQ in the Process group table under the tiles and click Details to display the ActiveMQ process group details.
The chart displays the selected process group metric over time. You can select a different metric from the list.
Click the Process group details button.
On the Process group details page, select the Technology-specific metrics tab.
Here you can identify any problematic nodes.
To access node-specific metrics, select a node from the Process list at the bottom of the page.
Drill down into the metrics of individual nodes to find the root causes of any potential bottlenecks or detected problems.
Click the ActiveMQ metrics tab. Here you’ll find valuable ActiveMQ node-specific metrics.
Pay particular attention to the Broker limits chart, which shows memory usage, storage usage, and any temporary storage limits that have been assigned to the broker.
Other important metrics include Connections, Number of producers, and Number of consumers. See ActiveMQ metrics for definitions.
Click the Queues metrics tab to display essential information about your queues.
Queues size informs you about traffic.
Average enqueue time increase informs you about ActiveMQ message processing-time degradation.
Be aware that Average enqueue time is calculated as an average of all messages created since the start of the broker session. When waiting time increases rapidly, this metric changes only slightly and is most helpful for trend analysis. For real-time usage, keep an eye on Average enqueue time increase.
|Average enqueue time||Average time (in milliseconds) from enqueue to dequeue of messages.|
|Average enqueue time increase||Increase of average enqueue time counted as the delta between samples. (The wait time of messages before they’re consumed.)|
|Memory usage||Percentage usage of memory limit for NON_PERSISTENT messages.|
|Store usage||Percentage usage of storage limit for PERSISTENT messages.|
|Temp usage||Percentage usage of storage limit for temporary messages.|
|Current connections||Number of currently open connections.|
|Total connections||Number of connections since last broker restart.|
|Queue size||Number of messages in the queue/store that haven’t been acknowledged by a consumer.|
|Enqueue count||Number of messages sent to the queue since the last restart.|
|Dequeue count||Number of messages removed from the queue (acknowledged by consumer) since last restart.|
|Dispatch count||Number of messages sent to consumer sessions (Dequeue + Inflight).|
|Expired count||Number of messages not delivered because they expired.|
|In Flight count||Number of messages sent to a consumer session that haven’t received an ack.|