The ActiveMQ check collects metrics for brokers, queues, producers, consumers, and more.
Note: This check also supports ActiveMQ Artemis (future ActiveMQ version 6
) and reports metrics under the activemq.artemis
namespace. See metadata.csv for a list of metrics provided by this integration.
Note: If you are running an ActiveMQ version older than 5.8.0, see the Agent 5.10.x released sample files.
The Agent's ActiveMQ check is included in the Datadog Agent package, so you don't need to install anything else on your ActiveMQ nodes.
The check collects metrics from JMX with JMXFetch. A JVM is needed on each node so the Agent can run JMXFetch. Datadog recommends using an Oracle-provided JVM.
To configure this check for an Agent running on a host:
-
Make sure that JMX Remote is enabled on your ActiveMQ server.
-
Configure the Agent to connect to ActiveMQ. Edit
activemq.d/conf.yaml
, in theconf.d/
folder at the root of your Agent's configuration directory. See the sample activemq.d/conf.yaml for all available configuration options. See themetrics.yaml
file for the list of default collected metrics.init_config: is_jmx: true collect_default_metrics: true instances: - host: localhost port: 1616 user: username password: password name: activemq_instance
Available for Agent versions >6.0
-
Collecting logs is disabled by default in the Datadog Agent, enable it in your
datadog.yaml
file:logs_enabled: true
-
Add this configuration block to your
activemq.d/conf.yaml
file to start collecting your ActiveMQ logs:logs: - type: file path: "<ACTIVEMQ_BASEDIR>/data/activemq.log" source: activemq service: "<SERVICE_NAME>" - type: file path: "<ACTIVEMQ_BASEDIR>/data/audit.log" source: activemq service: "<SERVICE_NAME>"
For containerized environments, see the Autodiscovery Integration Templates for guidance on applying the parameters below.
Parameter | Value |
---|---|
<INTEGRATION_NAME> |
activemq |
<INIT_CONFIG> |
"is_jmx": true |
<INSTANCE_CONFIG> |
{"host": "%%host%%","port":"1099"} |
Available for Agent versions >6.0
Collecting logs is disabled by default in the Datadog Agent. To enable it, see Kubernetes Log Collection.
Parameter | Value |
---|---|
<LOG_CONFIG> |
{"source": "activemq", "service": "<YOUR_APP_NAME>"} |
Run the Agent's status subcommand and look for activemq
under the Checks section.
See metadata.csv for a list of metrics provided by this integration. Metrics associated with ActiveMQ Artemis flavor have artemis
in their metric name, all others are reported for ActiveMQ "classic".
The ActiveMQ check does not include any events.
See service_checks.json for a list of service checks provided by this integration.
Need help? Contact Datadog support.
Additional helpful documentation, links, and articles: