Apache ActiveMQ Classic extension

  • Latest Dynatrace
  • Extension
  • Published Oct 27, 2025

Deliver smart, automated observability for ActiveMQ with trace and metric insights.

Analyze each broker individually to help you understand its performanceNavigate your entire ActiveMQ environment to help you understand relationships and give context to each metric
1 of 5

Get started

Overview

Monitor ActiveMQ performance with trace and metric insights for faster issue resolution.

With Dynatrace, you can get observability for ActiveMQ without touching any code, thanks to automatic monitoring. Seamless end-to-end traces for connected producer and consumer services allow you to diagnose anomalies and pinpoint the root cause of the broken code before your customers are affected. Comprehensive metrics give you insight into the health and performance of your ActiveMQ brokers, queues, and topics. Events point you to critical anomalies, reducing the mean time to repair.

Use cases

  • Capture every message across tiers without blind spots.
  • Troubleshoot asynchronous service problems across your stack proactively.
  • Improve the performance of your producer and consumer services end-to-end.
  • Prevent message processing anomalies to reduce the mean time to repair.
  • Monitor the health and performance of all your brokers, topics, and queues.

Requirements

Message clients (applications)

To get trace insight:

To get log insight:

Message servers (brokers)

Prerequisites:

To get metric insight:

  1. Install OneAgent on the virtual machine or server of your ActiveMQ broker process.
  2. Ensure you are monitoring the ActiveMQ broker process, and not the client-side.
  3. Activate the OneAgent feature Java Metric Extensions 2.0 (JMX).
  4. Select in Dynatrace Add to environment to configure the extension.
  5. Open the Apache ActiveMQ Overview dashboard.

How to properly capture the activeMQ.BrokerHealthStatus metric: Previous to versions 1.313 of the OneAgent, this metric would display an immutable value that does not reflect the reality. To correctly display this metric over time, please ensure your OneAgent is on version 1.313+

Feature sets

When activating your extension using monitoring configuration, you can limit monitoring to one of the feature sets. To work properly the extension has to collect at least one metric after the activation.

In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.

All metrics that aren't categorized into any feature set are considered to be the default and are always reported.

A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.

Metric nameMetric keyDescription
Broker healthactiveMQ.BrokerHealthStatus
Metric nameMetric keyDescription
Total consumer countactiveMQ.TotalConsumerCount
Total producer countactiveMQ.TotalProducerCount
Total connections countactiveMQ.TotalConnectionsCount
Current connections countactiveMQ.CurrentConnectionsCount
Metric nameMetric keyDescription
Memory usageactiveMQ.MemoryPercentUsage
Store usageactiveMQ.StorePercentUsage
Temp usageactiveMQ.TempPercentUsage
Metric nameMetric keyDescription
Average enqueue timeactiveMQ.AverageEnqueueTime
activeMQ.AverageEnqueueTimeIncrease
activeMQ.DequeueCount
Consumer countactiveMQ.ConsumerCount
activeMQ.DispatchCount
activeMQ.EnqueueCount
activeMQ.ExpiredCount
activeMQ.InFlightCount
Queue sizeactiveMQ.QueueSize
Related tags
ApplicationJMXMessage queueApacheApplication Observability