Amazon MQ Integration
Monitor managed ActiveMQ and RabbitMQ broker metrics, queue depth, and producer rates for your Amazon MQ infrastructure. Catch broker storage exhaustion and consumer dropout before messages are blocked or lost.
How It Works
Connect via CloudWatch Metric Streams
Deploy the TigerOps CloudFormation stack in your AWS account. It creates a Kinesis Firehose stream that forwards Amazon MQ CloudWatch metrics to TigerOps with sub-minute latency, covering both ActiveMQ and RabbitMQ broker types.
Configure Broker & Queue Scope
Specify which Amazon MQ brokers to monitor by name or tag. TigerOps auto-discovers all queues, topics (ActiveMQ), and virtual host exchanges (RabbitMQ) and begins collecting depth and throughput metrics immediately.
Set Queue Depth & Producer SLOs
Define per-queue depth limits and expected producer rate ranges. TigerOps alerts when queues grow beyond capacity, producer rates drop to zero, or consumer count falls below your minimum — detecting silent failures early.
Correlate with AWS Services
TigerOps links Amazon MQ metrics with the ECS tasks, Lambda functions, and EC2 instances consuming messages — correlating queue depth spikes with downstream service CPU exhaustion, OOM events, or deployment failures.
What You Get Out of the Box
Broker Health Monitoring
Track Amazon MQ broker CPU utilization, JVM heap usage, store percentage used, and network throughput. Alert when broker resources approach the limits that trigger Amazon MQ flow control or broker replacement.
Queue Depth Tracking
Per-queue message count, enqueue rate, and dequeue rate with historical trending. Detect when queues grow faster than consumers drain them and predict when depth will breach your configured SLO.
Producer & Consumer Rate Metrics
Monitor producer publish rates and consumer dispatch rates per queue. Alert when producer rates spike unexpectedly or consumer rates drop — both indicate queue health issues requiring investigation.
Durable Subscriber Backlog
For ActiveMQ topics, track durable subscription message counts and alert when offline durable subscribers accumulate large backlogs that will flood consumers when they reconnect.
RabbitMQ Virtual Host & Exchange Metrics
For Amazon MQ for RabbitMQ, track per-vhost message rates, exchange routing rates, and unroutable message counts. Alert when exchanges are dropping messages due to routing failures.
AI Root Cause Analysis
When Amazon MQ queue depth spikes, TigerOps AI correlates consumer service health (ECS task restarts, Lambda throttles), broker resource utilization, and upstream producer deploy events to identify the root cause.
CloudFormation Deployment
Deploy the TigerOps CloudWatch Metric Stream to begin collecting Amazon MQ broker metrics.
# Deploy TigerOps CloudWatch Metric Stream for Amazon MQ
aws cloudformation deploy \
--template-url https://tigerops-cfn.s3.amazonaws.com/metric-stream.yaml \
--stack-name tigerops-amazonmq-monitoring \
--capabilities CAPABILITY_IAM \
--parameter-overrides \
TigerOpsApiKey="${TIGEROPS_API_KEY}" \
TigerOpsEndpoint="https://ingest.atatus.net/cloudwatch/v1/stream" \
# Include both ActiveMQ and RabbitMQ namespaces
IncludeNamespaces="AWS/AmazonMQ" \
# Optional: include ECS/Lambda for consumer correlation
AdditionalNamespaces="AWS/ECS,AWS/Lambda"
# Verify the stream is running
aws cloudwatch describe-metric-streams \
--query "Entries[?Name=='tigerops-amazonmq-stream'].State"
# Configure per-broker alerts in TigerOps (tigerops.yaml)
integrations:
amazonMQ:
brokers:
- brokerName: "production-activemq"
brokerType: activemq
queueSLOs:
"payment.requests":
maxDepth: 5000
minConsumers: 2
producerRateDropAlertPct: 50
"order.events":
maxDepth: 10000
- brokerName: "production-rabbitmq"
brokerType: rabbitmq
vhosts:
- name: "/"
queueSLOs:
"notifications":
maxDepth: 1000Common Questions
Does TigerOps support both Amazon MQ for ActiveMQ and Amazon MQ for RabbitMQ?
Yes. TigerOps monitors both broker types. ActiveMQ brokers expose queue, topic, and durable subscriber metrics. RabbitMQ brokers expose queue, exchange, virtual host, and connection metrics. Both are collected via CloudWatch Metric Streams with identical setup.
How does TigerOps handle Amazon MQ active/standby broker deployments?
TigerOps monitors both the active and standby brokers in an active/standby pair. Failover events are detected when the standby becomes active, and TigerOps correlates the failover with any queue metric anomalies that preceded or followed the broker switch.
Can TigerOps alert when an Amazon MQ broker's storage is filling up?
Yes. TigerOps tracks the StorePercentUsage CloudWatch metric and fires a warning alert at 70% and a critical alert at 85% by default. Storage exhaustion causes Amazon MQ to block producers, so proactive alerting prevents message delivery failures.
How do I monitor Amazon MQ queues that are used by on-premises consumers?
TigerOps monitors the queue metrics from the broker side regardless of where consumers connect from. On-premises consumers connecting via MQTT, STOMP, or OpenWire appear as connections and their queue consumption rates are tracked identically to cloud consumers.
Does TigerOps support Amazon MQ network of brokers topologies?
For ActiveMQ, TigerOps monitors each broker in a network independently and tracks network bridge connector metrics. Cross-broker message forwarding rates and bridge connectivity status are visible, making it easier to diagnose cross-region routing failures.
Stop Discovering Amazon MQ Broker Issues After Producers Are Blocked
Broker storage alerts, queue depth SLOs, and consumer dropout detection. Deploy via CloudFormation in minutes.