Amazon CloudWatch metrics for Amazon Aurora - Amazon Aurora
Cluster-level metrics for Amazon AuroraInstance-level metrics for Amazon AuroraAmazon CloudWatch usage metrics for Amazon Aurora
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon CloudWatch metrics for Amazon Aurora

The AWS/RDS namespace includes the following metrics that apply to database entities running on Amazon Aurora. Some metrics apply to either Aurora MySQL, Aurora PostgreSQL, or both. Furthermore, some metrics are specific to a DB cluster, primary DB instance, replica DB instance, or all DB instances.

For Aurora global database metrics, see Amazon CloudWatch metrics for write forwarding. For Aurora parallel query metrics, see Monitoring parallel query.

Cluster-level metrics for Amazon Aurora

The following table describes metrics that are specific to Aurora clusters.

Amazon Aurora cluster-level metrics
Metric Console name Description Applies to Units

AuroraGlobalDBDataTransferBytes

Aurora Global DB Data Transfer Bytes (Bytes)

In an Aurora Global Database, the amount of redo log data transferred from the master Amazon Region to a secondary Amazon Region.

Aurora MySQL and Aurora PostgreSQL

Bytes

AuroraGlobalDBProgressLag

In an Aurora Global Database, the measure of how far the secondary cluster is behind the primary cluster for both user transactions and system transactions.

Aurora MySQL and Aurora PostgreSQL

Milliseconds

AuroraGlobalDBReplicatedWriteIO

Aurora Global DB Replicated Write IO

In an Aurora Global Database, the number of write I/O operations replicated from the primary Amazon Region to the cluster volume in a secondary Amazon Region. The billing calculations for the secondary Amazon Regions in a global database use VolumeWriteIOPs to account for writes performed within the cluster. The billing calculations for the primary Amazon Region in a global database use VolumeWriteIOPs to account for the write activity within that cluster, and AuroraGlobalDBReplicatedWriteIO to account for cross-Region replication within the global database.

Aurora MySQL and Aurora PostgreSQL

Count

AuroraGlobalDBReplicationLag

Aurora Global DB Replication Lag (Milliseconds)

For an Aurora Global Database, the amount of lag when replicating updates from the primary Amazon Region.

Aurora MySQL and Aurora PostgreSQL

Milliseconds

AuroraGlobalDBRPOLag

In an Aurora Global Database, the recovery point objective (RPO) lag time. This metric measures how far the secondary cluster is behind the primary cluster for user transactions.

Aurora MySQL and Aurora PostgreSQL

Milliseconds

AuroraVolumeBytesLeftTotal

The remaining available space for the cluster volume. As the cluster volume grows, this value decreases. If it reaches zero, the cluster reports an out-of-space error.

If you want to detect whether your Aurora MySQL cluster is approaching the size limit of 128 tebibytes (TiB), this value is simpler and more reliable to monitor than VolumeBytesUsed. AuroraVolumeBytesLeftTotal takes into account storage used for internal housekeeping and other allocations that don't affect your storage billing.

Aurora MySQL

Bytes

BacktrackChangeRecordsCreationRate

Backtrack Change Records Creation Rate (Count)

The number of backtrack change records created over 5 minutes for your DB cluster.

Aurora MySQL

Count per 5 minutes

BacktrackChangeRecordsStored

Backtrack Change Records Stored (Count)

The number of backtrack change records used by your DB cluster.

Aurora MySQL

Count

BackupRetentionPeriodStorageUsed

Backup Retention Period Storage Used (GiB)

The total amount of backup storage used to support the point-in-time restore feature within the Aurora DB cluster's backup retention window. This amount is included in the total reported by the TotalBackupStorageBilled metric. It is computed separately for each Aurora cluster. For instructions, see Understanding Amazon Aurora backup storage usage.

Aurora MySQL and Aurora PostgreSQL

Bytes

ServerlessDatabaseCapacity

The current capacity of an Aurora Serverless DB cluster.

Aurora MySQL and Aurora PostgreSQL

Count

SnapshotStorageUsed

Snapshot Storage Used (GiB)

The total amount of backup storage consumed by all Aurora snapshots for an Aurora DB cluster outside its backup retention window. This amount is included in the total reported by the TotalBackupStorageBilled metric. It is computed separately for each Aurora cluster. For instructions, see Understanding Amazon Aurora backup storage usage.

Aurora MySQL and Aurora PostgreSQL

Bytes

TotalBackupStorageBilled

Total Backup Storage Used (GiB)

The total amount of backup storage in bytes for which you are billed for a given Aurora DB cluster. The metric includes the backup storage measured by the BackupRetentionPeriodStorageUsed and SnapshotStorageUsed metrics. This metric is computed separately for each Aurora cluster. For instructions, see Understanding Amazon Aurora backup storage usage.

Aurora MySQL and Aurora PostgreSQL

Bytes

VolumeBytesUsed

Volume Bytes Used (GiB)

The amount of storage used by your Aurora DB instance.

This value affects the cost of the Aurora DB cluster (for pricing information, see the Amazon RDS product page).

This value doesn't reflect some internal storage allocations that don't affect storage billing. For Aurora MySQL you can anticipate out-of-space issues more accurately by testing whether AuroraVolumeBytesLeftTotal is approaching zero instead of comparing VolumeBytesUsed against the storage limit of 128 TiB.

Aurora MySQL and Aurora PostgreSQL

Bytes

VolumeReadIOPs

Volume Read IOPS (Count)

The number of billed read I/O operations from a cluster volume within a 5-minute interval.

Billed read operations are calculated at the cluster volume level, aggregated from all instances in the Aurora DB cluster, and then reported at 5-minute intervals. The value is calculated by taking the value of the Read operations metric over a 5-minute period. You can determine the amount of billed read operations per second by taking the value of the Billed read operations metric and dividing by 300 seconds. For example, if the Billed read operations returns 13,686, then the billed read operations per second is 45 (13,686 / 300 = 45.62).

You accrue billed read operations for queries that request database pages that aren't in the buffer cache and must be loaded from storage. You might see spikes in billed read operations as query results are read from storage and then loaded into the buffer cache.

Tip

If your Aurora MySQL cluster uses parallel query, you might see an increase in VolumeReadIOPS values. Parallel queries don't use the buffer pool. Thus, although the queries are fast, this optimized processing can result in an increase in read operations and associated charges.

Aurora MySQL and Aurora PostgreSQL

Count per 5 minutes

VolumeWriteIOPs

Volume Write IOPS (Count)

The number of write disk I/O operations to the cluster volume, reported at 5-minute intervals. For a detailed description of how billed write operations are calculated, see VolumeReadIOPs.

Aurora MySQL and Aurora PostgreSQL

Count per 5 minutes

Instance-level metrics for Amazon Aurora

The following instance-specific CloudWatch metrics apply to all Aurora MySQL and Aurora PostgreSQL instances unless noted otherwise.

Amazon Aurora instance-level metrics
Metric Console Name Description Applies to Units

AbortedClients

The number of client connections that have not been closed properly.

Aurora MySQL

Count

ActiveTransactions

Active Transactions (Count)

The average number of current transactions executing on an Aurora database instance per second.

By default, Aurora doesn't enable this metric. To begin measuring this value, set innodb_monitor_enable='all' in the DB parameter group for a specific DB instance.

Aurora MySQL

Count per second

AuroraBinlogReplicaLag

Aurora Binlog Replica Lag (Seconds)

The amount of time that a binary log replica DB cluster running on Aurora MySQL-Compatible Edition lags behind the binary log replication source. A lag means that the source is generating records faster than the replica can apply them.

This metric reports different values depending on the engine version:

Aurora MySQL version 2

The Seconds_Behind_Master field of the MySQL SHOW SLAVE STATUS

Aurora MySQL version 3

SHOW REPLICA STATUS

You can use this metric to monitor errors and replica lag in a cluster that acts as a binary log replica. The metric value indicates the following:

A high value

The replica is lagging the replication source.

0 or a value close to 0

The replica process is active and current.

-1

Aurora can't determine the lag, which can happen during replica setup or when the replica is in an error state.

Because binary log replication only occurs on the writer instance of the cluster, we recommend using the version of this metric associated with the WRITER role.

For more information about administering replication, see Replicating Amazon Aurora MySQL DB clusters across Amazon Web Services Regions. For more information about troubleshooting, see Amazon Aurora MySQL replication issues.

Primary for Aurora MySQL

Seconds

AuroraReplicaLag

Aurora Replica Lag (Milliseconds)

For an Aurora replica, the amount of lag when replicating updates from the primary instance.

Replica for Aurora MySQL and Aurora PostgreSQL

Milliseconds

AuroraReplicaLagMaximum

Replica Lag Maximum (Milliseconds)

The maximum amount of lag between the primary instance and any of the Aurora DB instance in the DB cluster.

Primary for Aurora MySQL and Aurora PostgreSQL

Milliseconds

AuroraReplicaLagMinimum

Replica Lag Minimum (Milliseconds)

The minimum amount of lag between the primary instance and any of the Aurora DB instance in the DB cluster.

Primary for Aurora MySQL and Aurora PostgreSQL

Milliseconds

AuroraSlowConnectionHandleCount

The number of connections that have waited beyond the value in aurora_connection_queued_time_warning_threshold to start the handshake.

Aurora MySQL

Count

AuroraSlowHandshakeCount

The number of connections that have taken the time beyond the value in aurora_connection_prepare_warning_threshold to finish the handshake.

Aurora MySQL

Count

BacktrackWindowActual

Backtrack Window Actual (Minutes)

The difference between the target backtrack window and the actual backtrack window.

Primary for Aurora MySQL

Minutes

BacktrackWindowAlert

Backtrack Window Alert (Count)

The number of times that the actual backtrack window is smaller than the target backtrack window for a given period of time.

Primary for Aurora MySQL

Count

BlockedTransactions

Blocked Transactions (Count)

The average number of transactions in the database that are blocked per second.

Aurora MySQL

Count per second

BufferCacheHitRatio

Buffer Cache Hit Ratio (Percent)

The percentage of requests that are served by the buffer cache.

Aurora MySQL and Aurora PostgreSQL

Percentage

CommitLatency

Commit Latency (Milliseconds)

The average duration of commit operations.

Aurora MySQL and Aurora PostgreSQL

Milliseconds

CommitThroughput

Commit Throughput (Count/Second)

The average number of commit operations per second.

Aurora MySQL and Aurora PostgreSQL

Count per second

ConnectionAttempts

Connection Attempts (Count)

The number of attempts to connect to an instance, whether successful or not.

Aurora MySQL and Aurora PostgreSQL

Count

CPUCreditBalance

CPU Credit Balance (Count)

The number of CPU credits that an instance has accumulated, reported at 5-minute intervals. You can use this metric to determine how long a DB instance can burst beyond its baseline performance level at a given rate.

This metric applies only to db.t2.small and db.t2.medium instances for Aurora MySQL, and to db.t3 instances for Aurora PostgreSQL.

Note

We recommend using the T DB instance classes only for development and test servers, or other non-production servers. For more details on the T instance classes, see DB instance class types.

Launch credits work the same way in Amazon RDS as they do in Amazon EC2. For more information, see Launch credits in the Amazon Elastic Compute Cloud User Guide for Linux Instances.

Aurora MySQL and Aurora PostgreSQL

Count

CPUCreditUsage

CPU Credit Usage (Count)

The number of CPU credits consumed during the specified period, reported at 5-minute intervals. This metric measures the amount of time during which physical CPUs have been used for processing instructions by virtual CPUs allocated to the DB instance.

This metric applies only to db.t2.small and db.t2.medium instances for Aurora MySQL, and to db.t3 instances for Aurora PostgreSQL.

Note

We recommend using the T DB instance classes only for development and test servers, or other non-production servers. For more details on the T instance classes, see DB instance class types.

Aurora MySQL and Aurora PostgreSQL

Count

CPUUtilization

CPU Utilization (Percent)

The percentage of CPU used by an Aurora DB instance.

Aurora MySQL and Aurora PostgreSQL

Percentage

DatabaseConnections

DB Connections (Count)

The number of client network connections to the database instance.

The number of database sessions can be higher than the metric value because the metric value doesn't include the following:

  • Sessions that no longer have a network connection but which the database hasn't cleaned up

  • Sessions created by the database engine for its own purposes

  • Sessions created by the database engine's parallel execution capabilities

  • Sessions created by the database engine job scheduler

  • Amazon Aurora connections

Aurora MySQL and Aurora PostgreSQL

Count

DDLLatency

DDL Latency (Milliseconds)

The average duration of requests such as example, create, alter, and drop requests.

Aurora MySQL

Milliseconds

DDLThroughput

DDL (Count/Second)

The average number of DDL requests per second.

Aurora MySQL

Count per second

Deadlocks

Deadlocks (Count)

The average number of deadlocks in the database per second.

Aurora MySQL and Aurora PostgreSQL

Count per second

DeleteLatency

Delete Latency (Milliseconds)

The average duration of delete operations.

Aurora MySQL

Milliseconds

DeleteThroughput

Delete Throughput (Count/Second)

The average number of delete queries per second.

Aurora MySQL

Count per second

DiskQueueDepth

Queue Depth (Count)

The number of outstanding read/write requests waiting to access the disk.

Aurora PostgreSQL

Count

DMLLatency

DML Latency (Milliseconds)

The average duration of inserts, updates, and deletes.

Aurora MySQL

Milliseconds

DMLThroughput

DML Throughput (Count/Second)

The average number of inserts, updates, and deletes per second.

Aurora MySQL

Count per second
EBSByteBalance%

EBS Byte Balance (Percent)

The percentage of throughput credits remaining in the burst bucket of your RDS database. This metric is available for basic monitoring only.

To find the instance sizes that support this metric, see the instance sizes with an asterisk (*) in the EBS optimized by default table in Amazon EC2 User Guide for Linux Instances. The Sum statistic is not applicable to this metric.

Aurora MySQL and Aurora PostgreSQL

Percent
EBSIOBalance%

EBS IO Balance (Percent)

The percentage of I/O credits remaining in the burst bucket of your RDS database. This metric is available for basic monitoring only.

To find the instance sizes that support this metric, see the instance sizes with an asterisk (*) in the EBS optimized by default table in Amazon EC2 User Guide for Linux Instances. The Sum statistic is not applicable to this metric.

This metric is different from BurstBalance. To learn how to use this metric, see Improving application performance and reducing costs with Amazon EBS-Optimized Instance burst capability.

Aurora MySQL and Aurora PostgreSQL

Percent

EngineUptime

Engine Uptime (Seconds)

The amount of time that the instance has been running.

Aurora MySQL and Aurora PostgreSQL

Seconds

FreeableMemory

Freeable Memory (MB)

The amount of available random access memory.

Aurora MySQL and Aurora PostgreSQL

Bytes

FreeLocalStorage

Free Local Storage (Bytes)

The amount of local storage available.

Unlike for other DB engines, for Aurora DB instances this metric reports the amount of storage available to each DB instance. This value depends on the DB instance class (for pricing information, see the Amazon RDS product page). You can increase the amount of free storage space for an instance by choosing a larger DB instance class for your instance.

(This doesn't apply to Aurora Serverless v2.)

Aurora MySQL and Aurora PostgreSQL

Bytes

InsertLatency

Insert Latency (Milliseconds)

The average duration of insert operations.

Aurora MySQL

Milliseconds

InsertThroughput

Insert Throughput (Count/Second)

The average number of insert operations per second.

Aurora MySQL

Count per second

LoginFailures

Login Failures (Count)

The average number of failed login attempts per second.

Aurora MySQL

Count per second

MaximumUsedTransactionIDs

MaximumUsedTransactionIDs

The age of the oldest unvacuumed transaction ID, in transactions. If this value reaches 2,146,483,648 (2^31 - 1,000,000), the database is forced into read-only mode, to avoid transaction ID wraparound. For more information, see Preventing transaction ID wraparound failures in the PostgreSQL documentation.

Aurora PostgreSQL

Count

NetworkReceiveThroughput

Network Receive Throughput (MB/Second)

The amount of network throughput received from clients by each instance in the Aurora MySQL DB cluster. This throughput doesn't include network traffic between instances in the Aurora DB cluster and the cluster volume.

Aurora MySQL and Aurora PostgreSQL

Bytes per second (console shows Megabytes per second)

NetworkThroughput

Network Throughput (Byte/Second)

The amount of network throughput both received from and transmitted to clients by each instance in the Aurora MySQL DB cluster. This throughput doesn't include network traffic between instances in the DB cluster and the cluster volume.

Aurora MySQL and Aurora PostgreSQL

Bytes per second

NetworkTransmitThroughput

Network Transmit Throughput (MB/Second)

The amount of network throughput sent to clients by each instance in the Aurora DB cluster. This throughput doesn't include network traffic between instances in the DB cluster and the cluster volume.

Aurora MySQL and Aurora PostgreSQL

Bytes per second (console shows Megabytes per second)

NumBinaryLogFiles

The number of binlog files generated.

 Aurora MySQL

Count

Queries

Queries (Count/Second)

The average number of queries executed per second.

Aurora MySQL

Count per second

RDSToAuroraPostgreSQLReplicaLag

The lag when replicating updates from the primary RDS PostgreSQL instance to other nodes in the cluster.

Replica for Aurora PostgreSQL

Seconds

ReadIOPS

Read IOPS (Count/Second)

The average number of disk I/O operations per second.

Aurora PostgreSQL-Compatible Edition reports read and write IOPS separately, in 1-minute intervals.

Aurora PostgreSQL

Count per second

ReadLatency

Read Latency (Milliseconds)

The average amount of time taken per disk I/O operation.

Aurora MySQL and Aurora PostgreSQL

Seconds

ReadThroughput

Read Throughput (MB/Second)

The average number of bytes read from disk per second.

Aurora PostgreSQL

Bytes per second

ReplicationSlotDiskUsage

The amount of disk space consumed by replication slot files.

Aurora PostgreSQL

Bytes

ResultSetCacheHitRatio

Result Set Cache Hit Ratio (Percent)

The percentage of requests that are served by the Resultset cache.

Aurora MySQL

Percentage

RollbackSegmentHistoryListLength

The undo logs that record committed transactions with delete-marked records. These records are scheduled to be processed by the InnoDB purge operation.

Aurora MySQL

Count

RowLockTime

The total time spent acquiring row locks for InnoDB tables.

Aurora MySQL

Milliseconds

SelectLatency

Select Latency (Milliseconds)

The average amount of time for select operations.

Aurora MySQL

Milliseconds

SelectThroughput

Select Throughput (Count/Second)

The average number of select queries per second.

Aurora MySQL

Count per second

StorageNetworkReceiveThroughput

Network Receive Throughput (MB/Second)

The amount of network throughput received from the Aurora storage subsystem by each instance in the DB cluster.

Aurora MySQL and Aurora PostgreSQL

Bytes per second

StorageNetworkThroughput

Network Throughput (Byte/Second)

The amount of network throughput received from and sent to the Aurora storage subsystem by each instance in the Aurora MySQL DB cluster.

Aurora MySQL and Aurora PostgreSQL

Bytes per second

StorageNetworkTransmitThroughput

Network Transmit Throughput (MB/Second)

The amount of network throughput sent to the Aurora storage subsystem by each instance in the Aurora MySQL DB cluster.

Aurora MySQL and Aurora PostgreSQL

Bytes per second

SumBinaryLogSize

The total size of the binlog files.

Aurora MySQL

Bytes

SwapUsage

Swap Usage (MB)

The amount of swap space used. This metric is available for the Aurora PostgreSQL DB instance classes db.t3.medium, db.t3.large, db.r4.large, db.r4.xlarge, db.r5.large, db.r5.xlarge, db.r6g.large, db.r6g.xlarge, db.t4g.medium, and db.t4g.large. For Aurora MySQL, this metric applies only to db.t* DB instance classes.

Aurora MySQL and Aurora PostgreSQL

Bytes

TransactionLogsDiskUsage

Transaction Logs Disk Usage (MB)

The amount of disk space consumed by transaction logs on the Aurora PostgreSQL DB instance.

This metric is generated only when Aurora PostgreSQL is using logical replication or Amazon Database Migration Service. By default, Aurora PostgreSQL uses log records, not transaction logs. When transaction logs aren't in use, the value for this metric is -1.

Primary for Aurora PostgreSQL

Bytes

UpdateLatency

Update Latency (Milliseconds)

The average amount of time taken for update operations.

Aurora MySQL

Milliseconds

UpdateThroughput

Update Throughput (Count/Second)

The average number of updates per second.

Aurora MySQL

Count per second

WriteIOPS

Write IOPS (Count/Second)

The number of Aurora storage write records generated per second. This is more or less the number of log records generated by the database. These do not correspond to 8K page writes, and do not correspond to network packets sent.

Aurora PostgreSQL

Count per second

WriteLatency

Write Latency (Milliseconds)

The average amount of time taken per disk I/O operation.

Aurora MySQL and Aurora PostgreSQL

Seconds

WriteThroughput

Write Throughput (MB/Second)

The average number of bytes written to persistent storage every second.

Aurora PostgreSQL

Bytes per second

Amazon CloudWatch usage metrics for Amazon Aurora

The AWS/Usage namespace in Amazon CloudWatch includes account-level usage metrics for your Amazon RDS service quotas. CloudWatch collects usage metrics automatically for all Amazon Web Services Regions.

For more information, see CloudWatch usage metrics in the Amazon CloudWatch User Guide. For more information about quotas, see Quotas and constraints for Amazon Aurora and Requesting a quota increase in the Service Quotas User Guide.

Metric Description Units*
DBClusterParameterGroups

The number of DB cluster parameter groups in your Amazon Web Services account. The count excludes default parameter groups.

Count
DBClusters

The number of Amazon Aurora DB clusters in your Amazon Web Services account.

Count
DBInstances

The number of DB instances in your Amazon Web Services account.

Count
DBParameterGroups

The number of DB parameter groups in your Amazon Web Services account. The count excludes the default DB parameter groups.

Count
DBSubnetGroups

The number of DB subnet groups in your Amazon Web Services account. The count excludes the default subnet group.

Count
ManualClusterSnapshots

The number of manually created DB cluster snapshots in your Amazon Web Services account. The count excludes invalid snapshots.

Count
OptionGroups

The number of option groups in your Amazon Web Services account. The count excludes the default option groups.

Count
ReservedDBInstances

The number of reserved DB instances in your Amazon Web Services account. The count excludes retired or declined instances.

Count

* Amazon RDS doesn't publish units for usage metrics to CloudWatch. The units only appear in the documentation.