Monitoring Amazon MQ

Note: Learn about the other supported AWS services with our AWS documentation.

Sensor (Data Collection)

Tracked Configuration

Broker Details
Created At
Engine Type
Engine Version
Instance Type
Public Accessibility
AWS Region


Broker Metrics Description
CpuCreditBalance The number of earned CPU credits that an instance has accrued since it was launched or started (including the number of launch credits)
CpuUtilization The percentage of allocated EC2 compute units that the broker currently uses.
CurrentConnectionsCount The current number of active connections on the current broker.
JournalFilesForFastRecovery The number of journal files that will be replayed after a clean shutdown.
JournalFilesForFullRecovery The number of journal files that will be replayed after an unclean shutdown.
HeapUsage The percentage of the ActiveMQ JVM memory limit that the broker currently uses.
NetworkIn The volume of incoming traffic for the broker.
NetworkOut The volume of outgoing traffic for the broker.
OpenTransactionsCount The total number of transactions in progress.
StorePercentUsage The percent used by the storage limit. If this reaches 100 the broker will refuse messages.
TotalConsumerCount The number of message consumers subscribed to destinations on the current broker.
TotalMessageCount The number of messages stored on the broker.
TotalProducerCount The number of message producers active on destinations on the current broker.
Destination Metrics Description
ConsumerCount The number of consumers subscribed to the destination.
EnqueueCount The number of messages sent to the destination.
EnqueueTime The amount of time it takes the broker to accept a message from the producer and send it to the destination.
ExpiredCount The number of messages that could not be delivered because they expired.
DispatchCount The number of messages sent to consumers.
DequeueCount The number of messages acknowledged by consumers.
MemoryUsage The percentage of the memory limit that the destination currently uses.
ProducerCount The number of producers for the destination.
QueueSize The number of messages in the queue. (This metric applies only to queues.)

Required Permissions

  • cloudwatch:GetMetricData
  • cloudwatch:GetMetricStatistics
  • mq:ListBrokers
  • mq:DescribeBroker


Metrics for Amazon MQ are pulled every 5 minutes, this can be changed via agent configuration (<agent_install_dir>/etc/instana/configuration.yaml):
  cloudwatch_period: 300

To disable monitoring of MQ instances use the following configuration:
  enabled: false

In order to enable in-depth metric monitoring, you need to inform the Agent about the queues/topics you want to monitor for every broker. You can configure it in the agent <agent_install_dir>/etc/instana/configuration.yaml:
    queues: # max 100 queues
      - 'queue1'
      - 'queue2'
    topics: # max 100 topics
      - 'topic1'

Monitoring multiple AWS accounts

Refer to the Monitoring multiple AWS accounts documentation to set up monitoring of multiple AWS accounts with one AWS agent in the same region.

To override which profiles should be used to monitor MQ, use the following configuration:
    - 'profile2'
    - 'profile3'

Note: Defining profiles on service level will override global AWS configuration.


Multiple tags can be defined, separated by a comma. Tags should be provided as a key-value pair separated by :. In order to make configuration easier, it is possible to define which tags you want to include in discovery or exclude from discovery. In case of defining tag in both lists (include and exclude), exclude list has higher priority. If there is no need for services filtering, the configuration should not be defined. It’s not mandatory to define all values in order to enable filtering.

Users are able to specify how often sensors will poll the AWS tagged resources using the tagged-services-poll-rate configuration property (default 300 seconds).

Note: Tags are only available in conjunction with the AWS Agent.

To define how often sensors will poll the tagged resources use following configuration:
  tagged-services-poll-rate: 60 #default 300

To include services by tags into discovery use following configuration:
  include_tags: # Comma separated list of tags in key:value format (e.g. env:prod,env:staging)

To exclude services by tags from discovery use following configuration:
  exclude_tags: # Comma separated list of tags in key:value format (e.g. env:dev,env:test)

Instana Agent Tags

Please note that tags are only available in conjunction with the AWS Agent. More details on using tags are described here.