The ActiveMQ check collects metrics for brokers and queues, producers and consumers, and more.

Note: If you are running a 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 via JMX, so you need a JVM on each node so the Agent can fork jmxfetch. We recommend using an Oracle-provided JVM.

1. Make sure that JMX Remote is enabled on your ActiveMQ server.

2. Configure the agent to connect to ActiveMQ. Edit activemq.d/conf.yaml, in the conf.d/ folder at the root of your Agent's configuration directory. See the sample activemq.d/conf.yaml for all available configuration options.

   instances:
     - host: localhost
       port: 7199
       user: username
       password: password
       name: activemq_instance
   # List of metrics to be collected by the integration
   # You should not have to modify this.
   init_config:
     conf:
       - include:
         Type: Queue
         attribute:
           AverageEnqueueTime:
             alias: activemq.queue.avg_enqueue_time
             metric_type: gauge
           ConsumerCount:
             alias: activemq.queue.consumer_count
             metric_type: gauge
           ProducerCount:
             alias: activemq.queue.producer_count
             metric_type: gauge
           MaxEnqueueTime:
             alias: activemq.queue.max_enqueue_time
             metric_type: gauge
           MinEnqueueTime:
             alias: activemq.queue.min_enqueue_time
             metric_type: gauge
           MemoryPercentUsage:
             alias: activemq.queue.memory_pct
             metric_type: gauge
           QueueSize:
             alias: activemq.queue.size
             metric_type: gauge
           DequeueCount:
             alias: activemq.queue.dequeue_count
             metric_type: counter
           DispatchCount:
             alias: activemq.queue.dispatch_count
             metric_type: counter
           EnqueueCount:
             alias: activemq.queue.enqueue_count
             metric_type: counter
           ExpiredCount:
             alias: activemq.queue.expired_count
             type: counter
           InFlightCount:
             alias: activemq.queue.in_flight_count
             metric_type: counter
   
       - include:
         Type: Broker
         attribute:
           StorePercentUsage:
             alias: activemq.broker.store_pct
             metric_type: gauge
           TempPercentUsage:
             alias: activemq.broker.temp_pct
             metric_type: gauge
           MemoryPercentUsage:
             alias: activemq.broker.memory_pct
             metric_type: gauge

3. Restart the agent

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.

The ActiveMQ check does not include any events.

activemq.can_connect: Returns CRITICAL if the Agent is unable to connect to and collect metrics from the monitored ActiveMQ instance. Returns OK otherwise.

Need help? Contact Datadog support.

Additional helpful documentation, links, and articles:

• ActiveMQ architecture and key metrics
• Monitor ActiveMQ metrics and performance