Logging is here!

ActiveMQ

Agent Check Agent Check

Supported OS: Linux Mac OS Windows

Overview

The ActiveMQ check lets you collect metrics for brokers and queues, producers and consumers, and more.

Note: If you are running a ActiveMQ version older than 5.8.0, refer to Agent 5.10.x released sample files.

Setup

Installation

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.

Configuration

  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 file, 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

Validation

Run the Agent’s status subcommand and look for activemq under the Checks section.

Data Collected

Metrics

The ActiveMQ check does not include any metrics at this time.

Events

The ActiveMQ check does not include any events at this time.

Service Checks

activemq.can_connect:

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

Troubleshooting

Need help? Contact Datadog Support.

Further Reading


Mistake in the docs? Feel free to contribute!

Activemq_xml Integration

Overview

Get metrics from ActiveMQ XML service in real time to:

  • Visualize and monitor ActiveMQ XML states
  • Be notified about ActiveMQ XML failovers and events.

Setup

Installation

The Activemq XML check is included in the Datadog Agent package, so you don’t need to install anything else on your servers.

Configuration

  1. Edit the activemq_xml.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory, to point to your server and port, set the masters to monitor.

    See the sample activemq_xml.d/conf.yaml for all available configuration options.

  2. Restart the Agent

Validation

Run the Agent’s status subcommand and look for activemq_xml under the Checks section.

Data Collected

Metrics

activemq.queue.avg_enqueue_time
(gauge)
On average the amount of time (ms) that messages remained enqueued.
shown as millisecond
activemq.queue.consumer_count
(gauge)
The number of consumers connected
activemq.queue.producer_count
(gauge)
The number of producers connected
activemq.queue.max_enqueue_time
(gauge)
The max the amount of time (ms) that messages remained enqueued.
shown as millisecond
activemq.queue.min_enqueue_time
(gauge)
The min the amount of time (ms) that messages remained enqueued.
shown as millisecond
activemq.queue.memory_pct
(gauge)
The percentage of memory currently in use
shown as percent
activemq.queue.size
(gauge)
The amount of messages that remained queued.
activemq.queue.dequeue_count
(gauge)
The amount of messages that remained dequeued.
activemq.queue.dispatch_count
(gauge)
The amount of messages that have been dispatched.
activemq.queue.enqueue_count
(gauge)
The amount of messages that have been enqueued.
activemq.queue.expired_count
(gauge)
The amount of messages that have been expired.
activemq.queue.in_flight_count
(gauge)
The amount of messages that have been in flight.
activemq.broker.store_pct
(gauge)
The percentage of store in use.
shown as percent
activemq.broker.temp_pct
(gauge)
The percentage of temporary in use.
shown as percent
activemq.broker.memory_pct
(gauge)
The percentage of memory in use.
shown as percent

Events

The ActiveMQ XML check does not include any events at this time.

Service Checks

The ActiveMQ XML check does not include any service checks at this time.

Troubleshooting

Need help? Contact Datadog Support.

Further Reading


Mistake in the docs? Feel free to contribute!