ActiveMQ Integration
Monitor queue and topic metrics, broker health, and message delivery rates across your ActiveMQ infrastructure. Catch queue depth spikes and consumer disconnects before messages pile up silently.
How It Works
Deploy activemq-exporter via Helm
Add the TigerOps Helm chart and configure the ActiveMQ broker's Jolokia or JMX endpoint. The exporter auto-discovers all queues, topics, and connector metrics without any broker configuration changes.
Configure Remote Write
Set your TigerOps remote-write endpoint and API key in the Helm values. Queue depth, enqueue/dequeue rates, in-flight messages, and broker memory usage begin flowing in within minutes.
Set Queue Depth Thresholds
Define per-queue depth and consumer count SLOs. TigerOps alerts when queue depth exceeds thresholds or when consumer count drops to zero — catching consumer crash events immediately.
Correlate Broker & Consumer Metrics
TigerOps links queue depth spikes with broker memory pressure, store usage, and consumer connection drops so you have full incident context without correlating dashboards manually.
What You Get Out of the Box
Queue Depth & Throughput
Per-queue message count, enqueue rate, dequeue rate, and in-flight message count. Historical depth trending with predictive alerts when queues are growing faster than consumers can drain them.
Topic Subscriber Metrics
Track durable and non-durable subscriber counts, subscription pending message counts, and topic dispatch rates. Alert when durable subscribers fall behind and backlog builds.
Broker Memory & Store Health
Monitor broker memory usage percentage, store usage percentage, and temp usage. ActiveMQ flow control kicks in at configurable thresholds — TigerOps warns you before producers are throttled.
Consumer Connection Monitoring
Track active consumer counts and connector open/close rates per queue and topic. Instant alerts when all consumers disconnect from a queue, preventing silent message accumulation.
Dead Letter Queue Tracking
Monitor the ActiveMQ Dead Letter Queue (DLQ) depth and per-destination DLQ accumulation. Alert when DLQ growth indicates a systemic message processing failure.
AI Root Cause Analysis
When queue depth spikes, TigerOps AI correlates broker GC pauses, consumer service error rates, network partition events, and database slowdowns from downstream consumers to identify the cause.
Helm Values for activemq-exporter
Deploy the TigerOps ActiveMQ exporter to your Kubernetes cluster with these Helm values.
# TigerOps activemq-exporter Helm values
# helm repo add tigerops https://charts.atatus.net
# helm install activemq-exporter tigerops/activemq-exporter -f values.yaml
activemqExporter:
# Jolokia endpoint (ActiveMQ Classic)
jolokiaUrl: http://activemq.messaging.svc.cluster.local:8161/api/jolokia
credentials:
usernameSecret:
name: activemq-credentials
key: username
passwordSecret:
name: activemq-credentials
key: password
# For ActiveMQ Artemis, use the management REST API instead
# artemisManagementUrl: http://artemis.messaging.svc.cluster.local:8161/console/jolokia
# Queues/topics to monitor (empty = monitor all)
queues:
- "payment.requests"
- "order.events"
- "notification.outbound"
topics:
- "inventory.updates"
- "audit.log"
# Dead Letter Queue name pattern
dlqPattern: "ActiveMQ.DLQ.*"
remoteWrite:
endpoint: https://ingest.atatus.net/api/v1/write
bearerToken: "${TIGEROPS_API_KEY}"
scrapeInterval: 15s
alerts:
queueDepthWarning: 1000
queueDepthCritical: 10000
consumerCountMinimum: 1 # alert if consumers drop below this
brokerMemoryUsagePct: 80
dlqDepthWarning: 10Common Questions
Which ActiveMQ versions does TigerOps support?
TigerOps supports Apache ActiveMQ Classic 5.x and Apache ActiveMQ Artemis 2.x. Metrics are collected via Jolokia REST API (Classic) or the Artemis management REST API. Amazon MQ for ActiveMQ is also supported via CloudWatch metric forwarding.
Does TigerOps require JMX access to ActiveMQ brokers?
Not necessarily. TigerOps prefers the Jolokia REST bridge (bundled with ActiveMQ Classic by default) over raw JMX. If Jolokia is disabled, the exporter can fall back to JMX via the standard RMI port. ActiveMQ Artemis uses its management REST API, so no JMX is needed.
Can TigerOps monitor ActiveMQ broker networks (broker meshes)?
Yes. TigerOps discovers all brokers in a network of brokers and collects per-broker queue and topic metrics. Network connector metrics — forwarded message counts and network bridge health — are also collected to help diagnose cross-broker routing issues.
How do I monitor ActiveMQ message expiry and TTL behavior?
TigerOps tracks expired message counts per destination. You can set alerts on high message expiry rates, which indicate producers are setting TTLs that consumers cannot meet — a leading indicator of consumer underprovisioning.
Does TigerOps support ActiveMQ Artemis address and anycast metrics?
Yes. For ActiveMQ Artemis, TigerOps collects metrics for both anycast (queue semantics) and multicast (topic semantics) addresses. Routing type, binding counts, message counts, and consumer counts are tracked per address and per queue within an address.
Stop Discovering Queue Depth Problems After Flow Control Kicks In
Queue depth SLOs, broker memory alerts, and consumer drop detection. Deploy in 5 minutes.