# Amazon EBS detailed performance statistics
Amazon EBS NVMe block devices vend real-time, high-resolution I/O performance statistics for Amazon EBS volumes attached to Nitro-based Amazon EC2 instances. These statistics are presented as aggregated counters that are retained for the duration of the volume's attachment to the instance. The statistics provide details about the cumulative number of operations, bytes sent and received, and time spent on read and write I/O operations. Additionally, the statistics include histograms for read and write I/O operations, and the total time your application has exceeded the EBS volume or attached instance's provisioned IOPS or throughput limits.
You can collect these statistics at a granularity of up to 1 second intervals. If requests are made more frequently than 1 second intervals, the NVMe driver might queue the requests, along with other admin commands, to be processed at a later time.
**Considerations**
+ The statistics are supported for all Amazon EBS volume types.
+ The statistics are supported only for volumes attached to [instances built on the Amazon Nitro System](https://docs.amazonaws.cn/ec2/latest/instancetypes/ec2-nitro-instances.html).
+ The statistics are available for Multi-Attach enabled volumes. When viewing statistics for a Multi-Attach enabled volume, the statistics are specific to that instance attachment, and reflect only that instance's usage.
+ The statistics are available at no additional cost.
## Statistics
The Amazon EBS NVMe block device vends the following statistics:
| Statistic name | Full name | Type | Description |
| --- | --- | --- | --- |
| total\_read\_ops | Total read operations | Counter | The total number of completed read operations. |
| total\_write\_ops | Total write operations | Counter | The total number of completed write operations. |
| total\_read\_bytes | Total read bytes | Counter | The total number of read bytes transferred. |
| total\_write\_bytes | Total write bytes | Counter | The total number of write bytes transferred. |
| total\_read\_time | Total read time | Counter | The total time spent, in microseconds, by all completed read operations. |
| total\_write\_time | Total write time | Counter | The total time spent, in microseconds, by all completed write operations. |
| ebs\_volume\_performance\_exceeded\_iops | Total time demand exceeded volume provisioned IOPS | Counter | The total time, in microseconds, that IOPS demand exceeded the volume's provisioned IOPS performance. |
| ebs\_volume\_performance\_exceeded\_tp | Total time demand exceeded volume provisioned throughput | Counter | The total time, in microseconds, that throughput demand exceeded the volume's provisioned throughput performance. |
| ec2\_instance\_ebs\_performance\_exceeded\_iops | Total time demand exceeded EC2 instance's IOPS performance | Counter | The total time, in microseconds, that the EBS volume exceeded the attached Amazon EC2 instance's maximum IOPS performance. |
| ec2\_instance\_ebs\_performance\_exceeded\_tp | Total time demand exceeded EC2 instance's throughput performance | Counter | The total time, in microseconds, that the EBS volume exceeded the attached Amazon EC2 instance's maximum throughput performance. |
| volume\_queue\_length | Volume queue length | Point in time | The number of read and write operations waiting to be completed. |
| read\_io\_latency\_histogram | Read I/O histogram | Histogram \* | The number of read operations completed within each latency bin, in microseconds. |
| write\_io\_latency\_histogram | Write I/O histogram | Histogram \* | The number of write operations completed within each latency bin, in microseconds. |
**Note**
\* Histogram statistics represent only I/O operations that have completed successfully. Stalled or impaired I/O operations are not included, but will be evident in the `volume_queue_length` statistics, which is presented as a point-in-time statistic.
## Accessing the statistics
The statistics must be accessed directly from the instance to which the Amazon EBS volume is attached. You can access the statistics using one of the following methods.
### Linux instances
------
#### [ Amazon CloudWatch ]
You can configure the Amazon CloudWatch agent to collect the statistics from your instance and make them available as custom metrics in CloudWatch. You can then use the metrics in CloudWatch to analyze I/O patterns, track performance trends, create custom dashboards, and set up automated alarms based on performance thresholds.
For more information about configuring the CloudWatch agent, see the following:
+ [ Create the CloudWatch agent configuration file](https://docs.amazonaws.cn/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-Configuration-File-Details.html)
+ [ Collect Amazon EBS NVMe driver metrics](https://docs.amazonaws.cn/AmazonCloudWatch/latest/monitoring/Container-Insights-metrics-EBS-Collect.html)
With the Amazon CloudWatch Observability EKS add-on version `4.1.0` and later, the statistics are automatically collected when the Amazon EBS CSI driver metrics are enabled. For more information, see [ Amazon EBS NVMe driver metrics](https://docs.amazonaws.cn/AmazonCloudWatch/latest/monitoring/Container-Insights-metrics-enhanced-EKS.html#Container-Insights-metrics-EBS).
------
#### [ ebsnvme script ]
The `ebsnvme` script can be found in the [ amazon-ec2-utils Github repo](https://github.com/amazonlinux/amazon-ec2-utils).
**To access the statistics**
1. Connect to the instance to which the volume is attached.
1. Download the `ebsnvme` script from the `amazon-ec2-utils` Github repo.
```
wget https://raw.githubusercontent.com/amazonlinux/amazon-ec2-utils/refs/heads/main/ebsnvme
```
1. Modify the permissions for the script to make it executable.
```
sudo chmod +x ./ebsnvme
```
1. Run the `ebsnvme` script and specify the device name for the volume.
```
sudo ./ebsnvme stats /dev/{{nvme0n1}}
```
------
#### [ nvme-cli tool ]
**To access the statistics**
1. Connect to the instance to which the volume is attached.
1. Amazon Linux AMIs released after November 12, 2024 include the latest version of the `nvme-cli` tool. If you are using an older Amazon Linux AMI, update the `nvme-cli` tool.
```
sudo yum install nvme-cli
```
1. Run the following command and specify the device name for the volume.
```
nvme amzn stats /dev/{{nvme0n1}}
```
------
#### [ Prometheus ]
You can monitor the statistics with Prometheus, an open-source monitoring application, and Amazon Managed Service for Prometheus. This makes it easier to monitor Amazon EBS volumes across container and Kubernetes environments at scale. With Amazon EBS CSI driver version v1.37.0 and later, the detailed performance statistics are exposed as a Prometheus-compatible `/metrics` endpoint for exporting into Prometheus.
For more information, see [Ingest metrics to your Amazon Managed Service for Prometheus workspace](https://docs.amazonaws.cn/prometheus/latest/userguide/AMP-ingest-methods.html) in the *Amazon Managed Service for Prometheus User Guide*.
------
### Windows instances
------
#### [ nvme\_amzn.exe tool ]
**To access the statistics**
1. Connect to the instance to which the volume is attached.
1. Make sure that you're using AWSNVMe driver version `1.7.0` or later. For more information about updating the AWSNVMe driver, see [Amazon NVMe drivers](https://docs.amazonaws.cn/AWSEC2/latest/UserGuide/aws-nvme-drivers.html).
1. Get the disk number for the EBS volume. For more information, see [Map Amazon EBS volumes to NVMe device names](https://docs.amazonaws.cn/ebs/latest/userguide/identify-nvme-ebs-device.html)
1. Run the following command as Administrator and specify the disk number for the volume.
```
.\nvme_amzn.exe stats {{disk_number}}
```
------