• EnglishEspañol日本語한국어Português
  • Log inStart now

Amazon SQS monitoring integration


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.

New Relic's infrastructure integrations include an integration for reporting your Amazon SQS data to New Relic. This document explains how to activate the integration and describes the data reported.


Amazon Simple Queue Service (Amazon SQS) provides hosted queues for storing messages in transit. New Relic's SQS integration reports queue-related data such as the count of messages delivered, delayed, and received, message size, and other metrics. SQS data is available in pre-built and you can also create custom queries and charts. You can also create alert conditions to notify you of changes in SQS data.

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 SQS integration:

  • New Relic polling interval: 5 minutes
  • AWS CloudWatch data interval: 1 minute

Find and use data

To find your integration data, go to one.newrelic.com > All capabilities > Infrastructure > AWS and select one of the SQS integration links.

You can query and explore your data using the QueueSample event type, with a provider value of SqsQueue.

For more on how to use your data, see Understand integration data.

Metric data

This integration collects the following Amazon SQS metrics. For full metric descriptions, see Amazon's SQS documentation.




The approximate age of the oldest non-deleted message in the queue, in seconds. For dead letter queues, this value is the longest time that a message has been in the queue.


The approximate number of messages in the queue that are delayed and not available for reading immediately. This can happen when the queue is configured as a delay queue or when a message has been sent with a delay parameter.


The approximate number of messages that are "in flight." Messages are considered in flight if they have been sent to a client but have not yet been deleted or have not yet reached the end of their visibility window.


The approximate number of messages available for retrieval from the queue.


The number of ReceiveMessage API calls that did not return a message.


The number of messages deleted from the queue.


The number of messages returned by calls to the ReceiveMessage API action.


The number of messages added to a queue.


The size in bytes of messages added to a queue.

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.