Amazon EBS monitoring integration

New Relic infrastructure integrations include an Amazon EBS integration for reporting your EBS data to New Relic. Here we explain how to activate our integration and what data can be reported.


Amazon Elastic Block Store (EBS) provides block level storage volumes for your Amazon EC2 instances. With New Relic's EBS integration, you'll be able to monitor writes per volume, volume counts, configuration options, and more. You'll be able to create custom charts of your data and create alert conditions based on changes in EBS data or configuration.

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

  • New Relic polling interval: 15 minutes
  • Amazon CloudWatch data interval: 1 minute or 5 minutes, depending on volume type

Find and use data

To find this integration's data, go to > Infrastructure > AWS and select one of the Amazon EBS integration links.

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

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

Metric data

This New Relic infrastructure integration collects the following Amazon EBS data:

For full descriptions of each metric, see Amazon's EBS Dimensions and Metrics.

Name Data type









volumeIdleTime seconds
volumeQueueLength integer/count
volumeThroughputPercentage percent
volumeConsumedReadWriteOps count
burstBalance percent

Inventory data

The Amazon EBS integration can report these EBS configuration options as inventory data:

Data indicated with an asterisk * is only fetched if extended inventory collection is on.

Name Description
attachmentState The attachment state, which can be shown as attaching, attached, detaching, or detached.

I/O operations were automatically enabled on this volume after an event occurred.

For more information, see Working with the AutoEnableIO Volume Attribute and Monitoring Volume Events.

availabilityZone The Availability Zone in which the volume lives.

For more information, see Resource Locations.


For more information, see Preserving Amazon EBS Volumes on Instance Termination.


For more information see Device Naming on Linux Instances.


For more information, see Amazon EBS Encryption.

instanceId The ID of the instance.
ioEnabled I/O operations were explicitly enabled for this volume.

For more information on General Purpose SSD baseline performance, I/O credits, and bursting, see Amazon EBS Volume Types in the Amazon Elastic Compute Cloud User Guide.

Constraint: Range is 100 to 20000 IOPS for io1 volumes and 100 to 10000 IOPS for gp2 volumes.

Condition: This parameter is required for requests to create io1 volumes; it is not used in requests to create gp2, st1, sc1, or standard volumes.

state "in-use", "error"

Volume status checks help you understand your impaired Amazon EBS volumes, and how inconsistent volume is handled.

Valid values are:

  • ok
  • warning
  • impaired
  • insufficient-data

For more information, see Monitoring volumes with status checks.


For additional information, see Amazon EBS volume types.

For more help

If you need more help, check out these support and learning resources: