Monitoring ActiveMQ Artemis
The ActiveMQ Artemis sensor is automatically deployed and installed after you install the Instana agent.
Supported Versions
Confirmed support for metrics and configuration data for versions: 2.0.0 to 2.6.x. By supporting these versions of Artemis, Instana supports JBoss AMQ version 7 and later.
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.
You can enable JMX access by removing <authorisation>
element from /apache-artemis/bin/myinstance/etc/management.xml
.
Configuration
To enable in-depth metric monitoring, add the queues that you want to monitor to the agent config file <agent_install_dir>/etc/instana/configuration.yaml
:
com.instana.plugin.activemqartemis:
monitorQueues:
- 'test-queue'
- 'DLQ'
Metrics collection
To view the metrics, select Infrastructure in the sidebar of the Instana User interface, click a specific monitored host, and then you can see a host dashboard with all the collected metrics and monitored processes.
Configuration data
- Version
- Broker Name
- Node ID
- Ports
- Memory Limit
- Addresses
- Queues
- Transport Acceptors
Performance metrics
Broker wide
Metric | Description | Granularity |
---|---|---|
Messages Added | Number of messages that are added to the broker and is collected from activemq.artemis:broker#TotalMessagesAdded . |
1 second |
Messages Acknowledged | Number of messages that are acknowledged (and removed) from the broker and is collected from activemq.artemis:broker#TotalMessagesAcknowledged . |
1 second |
Messages Expired | Number of messages that are expired on the broker and is collected from the sum of subcomponent=queues#MessagesExpired for all queues. |
1 second |
Messages stopped | Number of messages that are stopped on the broker to exceeding the max delivery attempts and is collected from the sum of subcomponent=queues#MessagesKilled for all queues. |
1 second |
Message Count | Message count on all queues and is collected from the sum of subcomponent=queues#MessageCount for all queues. |
1 second |
Total Connections | Number of total connections on the broker and is collected from activemq.artemis:broker#ConnectionCount . |
1 second |
Total Consumers | Number of total consumers on the broker and is collected from activemq.artemis:broker#TotalConsumerCount . |
1 second |
Memory Usage | Percent of memory limit that is used by all addresses on broker and is collected from activemq.artemis:broker#AddressMemoryUsagePercentage . |
1 second |
Queues
Metric | Description | Granularity |
---|---|---|
Message Count | Number of messages currently in this queue (includes scheduled, paged, and in-delivery messages) and is collected from subcomponent=queues#MessageCount . |
1 second |
Messages Added | Number of messages that are added to the queue and is collected from subcomponent=queues#MessagesAdded . |
1 second |
Messages Acknowledged | Number of messages that are acknowledged (and removed) from the queue and is collected from subcomponent=queues#MessagesAcknowledged . |
1 second |
Messages Expired | Number of messages that are expired on this queue and is collected from subcomponent=queues#MessagesExpired . |
1 second |
Messages stopped | Number of messages that are stopped on this queue due to exceeding the max delivery attempts and is collected from subcomponent=queues#MessagesKilled . |
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 that depend 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 entity.
For information about built-in events for the ActiveMQ Artemis sensor, see Built-in events reference.