중요
Enable the AWS CloudWatch Metric Streams integration to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option.
ActiveMQ is the only MQ engine supported by this integration. If you're using RabbitMQ, see our RabbitMQ integration on how to get metrics from your instance.
New Relic offers an integration for reporting your Amazon Web Services MQ data. This document explains how to activate this integration and describes the data that can be reported.
Activate integration
To enable this integration, follow standard procedures to connect AWS services to New Relic.
Configuration and polling
You can change the polling frequency and filter data using configuration options.
Default polling information for the Amazon MQ integration:
- New Relic polling interval: 5 minutes
- Amazon CloudWatch data interval: 1 minute
View and query data
To view your integration data, go to one.newrelic.com > All capabilities > Infrastructure > AWS and select an integration.
You can query and explore your data using the following event type:
Entity | Event Type | Provider |
|---|---|---|
Broker |
|
|
Topic |
|
|
Queue |
|
|
For more on how to use your data, see Understand and use integration data.
Metric data
This integration records Amazon MQ data for broker, topic, and queue entities.
MQ Broker data
Metric | Unit | Description |
|---|---|---|
| Count | The number of earned CPU credits that an instance has accrued since it was launched or started (including the number of launch credits). The credit balance is available for the broker instance to spend on bursts beyond the baseline CPU utilization. This metric is available only for the mq.t2.micro broker instance type. CPU credit metrics are available only at five-minute intervals. |
| Percent | The percentage of allocated EC2 compute units that the broker currently uses. |
| Count | The current number of active connections on the current broker. |
| Count | The total number of connections, active and inactive, that have been established on the broker. |
| Count | The number of inactive durable topic subscribers, up to a maximum of 2000. |
| Count | The number of journal files that will be replayed after a clean shutdown. |
| Count | The number of journal files that will be replayed after an unclean shutdown. |
| Percent | The percentage of the ActiveMQ JVM memory limit that the broker currently uses. |
| Bytes | The volume of incoming traffic for the broker. |
| Bytes | The volume of outgoing traffic for the broker. |
| Count | The total number of transactions in progress. |
| Percent | The percent used by the storage limit. If this reaches 100 the broker will refuse messages. |
| Count | The number of message consumers subscribed to destinations on the current broker. |
| Count | The number of messages stored on the broker. |
| Count | The number of message producers active on destinations on the current broker. |
MQ Topic data
Metric | Unit | Description |
|---|---|---|
| Count | The number of consumers subscribed to the destination. |
| Count | The number of messages sent to the destination, per minute. |
| Milliseconds | The end-to-end latency from when a message arrives at a broker until it is delivered to a consumer. |
| Count | The number of messages that couldn't be delivered because they expired, per minute. |
| Count | The number of messages sent to consumers, per minute. |
| Count | The number of messages acknowledged by consumers, per minute. |
| Count | The number of messages that have been received from the remote broker for a duplex network connector. |
| Count | The number of messages sent to consumers that have not been acknowledged. |
| Percent | The percentage of the memory limit that the destination currently uses. |
| Count | The number of producers for the destination. |
MQ Queue data
Metric | Unit | Description |
|---|---|---|
| Count | The number of consumers subscribed to the destination. |
| Count | The number of messages sent to the destination, per minute. |
| Milliseconds | The end-to-end latency from when a message arrives at a broker until it is delivered to a consumer. |
| Count | The number of messages that couldn't be delivered because they expired, per minute. |
| Count | The number of messages sent to consumers, per minute. |
| Count | The number of messages acknowledged by consumers, per minute. |
| Count | The number of messages that have been received from the remote broker for a duplex network connector. |
| Count | The number of messages sent to consumers that have not been acknowledged. |
| Percent | The percentage of the memory limit that the destination currently uses. |
| Count | The number of producers for the destination. |
| Count | The number of messages in the queue. |