重要
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 integrations include an Amazon EFS integration for reporting your EFS data to New Relic. This document explains the integration's features, how to activate it, and what data can be reported.
Features
With New Relic's integration for monitoring AWS Elastic File System (EFS), you can monitor EFS file system size, read/write operations, I/O capacity, throughput, and more. AWS integration data is also available for analysis, queries, and chart creation.
If connected through a VPC, you can also use the EFS file system with your own on-premise servers, which allows you to share file systems across different applications hosted on hybrid solutions.
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 EFS integration:
- New Relic polling interval: 5 minutes
- Amazon CloudWatch data interval: 1 minute or 5 minutes
Find and use data
To find this integration's data, go to one.newrelic.com > All capabilities > Infrastructure > AWS and select one of the Amazon EFS integration links.
You can query and explore your data using the BlockDeviceSample
event type, with a provider
value of EfsFileSystem
.
For more on how to find and use integration data, see Understand integration data.
Metric data
This integration collects the following Amazon EFS metrics:
Metric | Description |
---|---|
| The number of burst credits that a file system has. Burst credits allow a file system to burst to throughput levels above a file system’s baseline level for periods of time. For more information, see Throughput scaling in Amazon EFS. The Units: Bytes Valid statistics: |
| The number of client connections to a file system. When using a standard client, there is one connection per mounted Amazon EC2 instance. Note: To calculate the average Units: Count of client connections Valid statistics: |
| The number of bytes for each file system read operation. The Units:
|
| The number of bytes for each file system write operation. The Units:
|
| The number of bytes for each metadata operation. The Units:
|
| Shows how close a file system is to reaching the I/O limit of the General Purpose performance mode. If this metric is at 100% more often than not, consider moving your application to a file system using the Max I/O performance mode. Note: This metric is only submitted for file systems using the General Purpose performance mode. Units: Percent |
| The maximum amount of throughput a file system is allowed, given the file system size and The Units: Bytes per second Valid statistics: |
| The number of bytes for each file system operation, including data read, data write, and metadata operations. The Note: To calculate the average operations per second for a period, divide the Units:
|