Monitoring ActiveMQ
TABLE OF CONTENTS
Supported Versions
Confirmed support for metrics and configuration data for versions: 5.11.1, 5.12.0, 5.13.1, 5.14.3, 5.15.2.
Enable JMX
If JMX is not enabled, the following message is displayed in the UI:
Jmx is not enabled.
You can enable it in activemq config by setting the broker property useJmx to true.For information on how to enable JMX support with the broker property useJmx="true", see the ActiveMQ documentation.
Configuration
To enable in-depth metric monitoring, add the queues/topics you want to monitor to the agent configuration file <agent_install_dir>/etc/instana/configuration.yaml:
com.instana.plugin.activemq:
monitorQueues:
- 'test-queue-1'
- 'DLQ.test-1'
monitorTopics:
- 'ActiveMQ.Advisory.Topic'
- 'test-topic-1'Metrics collection
Configuration data
- Version
- Broker Name
- Health Status
- Ports
- Role
- Memory Limit
- Store Limit
- Topics
- Queues
- Transport Connectors
Performance metrics
Broker wide
| Metric | Description | Granularity |
|---|---|---|
| All Topics Messages Enqueue | Number of messages that have been sent to the broker and is collected from BrokerMBean#TotalEnqueueCount. |
1 second |
| All Topics Messages Dequeue | Number of messages that have been acknowledged on the broker and is collected from BrokerMBean#TotalDeque. |
1 second |
| All Queues Messages Enqueue | Amount of messages that have been sent to all queues and is collected from the sum of BrokerMBean#EnqueueCount for all queues. |
1 second |
| All Queues Messages Dequeue | Amount of messages that have been acknowledged on all queues and is collected from the sum of BrokerMBean#DequeueCount for all queues. |
1 second |
| Total Connections | Number of total connections on the broker and is collected from the BrokerMBean,connector=clientConnectors#connectionCount sum. |
1 second |
| Total Producers | Number of message producers active on destinations on the broker and is collected from BrokerMBean#TotalProducerCount. |
1 second |
| Total Consumers | Number of message consumers subscribed to destinations on the broker and is collected from BrokerMBean#TotalConsumerCount. |
1 second |
| Memory usage | Percent of memory limit used and is collected from BrokerMBean#MemoryPercentUsage. |
1 second |
| Store usage | Percent of store limit used and is collected from BrokerMBean#StorePercentUsage. |
1 second |
Topics
| Metric | Description | Granularity |
|---|---|---|
| Producer count | Number of producers attached to the topic and is collected from BrokerMBean,destinationType=Topic#ProducerCount. |
1 second |
| Consumer count | Number of consumers subscribed to the topic and is collected from BrokerMBean,destinationType=Topic#ConsumerCount. |
1 second |
| Messages Enqueued | Number of messages that have been sent to the topic and is collected from BrokerMBean,destinationType=Topic#EnqueueCount. |
1 second |
| Messages Dequeued | Number of messages that has been acknowledged (and removed) from the topic and is collected from BrokerMBean,destinationType=Topic#DequeueCount. |
1 second |
| Memory Usage | Percent of memory limit used and is collected from BrokerMBean,destinationType=Topic#MemoryPercentUsage. |
1 second |
Queues
| Metric | Description | Granularity |
|---|---|---|
| Queue size | Number of messages on this queue, including any that have been dispatched but not acknowledged and is collected from BrokerMBean,destinationType=Queue#QueueSize. |
1 second |
| Messages Enqueued | Number of messages that have been sent to the queue and is collected from BrokerMBean,destinationType=Queue#EnqueueCount. |
1 second |
| Messages Dequeued | Number of messages that has been acknowledged (and removed) from the queue and is collected from BrokerMBean,destinationType=Queue#DequeueCount. |
1 second |
| Memory Usage | Percent of memory limit used and is collected from BrokerMBean,destinationType=Queue#MemoryPercentUsage. |
1 second |
Health Signatures
For each sensor, there is a curated knowledgebase of health signatures that are evaluated continuously against the incoming metrics and are used to raise issues or incidents depending on user impact.
Built-in events trigger issues or incidents based on failing health signatures on entities, and custom events trigger issues or incidents based on the thresholds of an individual metric of any given entity.
For information about built-in events for the ActiveMQ sensor, see the Built-in events reference.