Enhanced Monitoring

Amazon RDS provides metrics in real time for the operating system (OS) that your DB instance runs on. You can view the metrics for your DB instance using the console, or consume the Enhanced Monitoring JSON output from Amazon CloudWatch Logs in a monitoring system of your choice.

By default, Enhanced Monitoring metrics are stored in the CloudWatch Logs for 30 days. To modify the amount of time the metrics are stored in the CloudWatch Logs, change the retention for the RDSOSMetrics log group in the CloudWatch console. For more information, see Change Log Data Retention in CloudWatch Logs in the Amazon CloudWatch Logs User Guide.

The cost for using Enhanced Monitoring depends on several factors:

You are only charged for Enhanced Monitoring that exceeds the free tier provided by Amazon CloudWatch Logs.

For more information about pricing, see Amazon CloudWatch Pricing.
A smaller monitoring interval results in more frequent reporting of OS metrics and increases your monitoring cost.
Usage costs for Enhanced Monitoring are applied for each DB instance that Enhanced Monitoring is enabled for. Monitoring a large number of DB instances is more expensive than monitoring only a few.
DB instances that support a more compute-intensive workload have more OS process activity to report and higher costs for Enhanced Monitoring.

Enhanced Monitoring Availability

Enhanced Monitoring is available for the following database engines:

MariaDB
Microsoft SQL Server
MySQL version 5.5 or later
Oracle
PostgreSQL

Enhanced Monitoring is available for all DB instance classes except for db.m1.small.

Differences Between CloudWatch and Enhanced Monitoring Metrics

CloudWatch gathers metrics about CPU utilization from the hypervisor for a DB instance, and Enhanced Monitoring gathers its metrics from an agent on the instance. As a result, you might find differences between the measurements, because the hypervisor layer performs a small amount of work. The differences can be greater if your DB instances use smaller instance classes, because then there are likely more virtual machines (VMs) that are managed by the hypervisor layer on a single physical instance. Enhanced Monitoring metrics are useful when you want to see how different processes or threads on a DB instance use the CPU.

Setting Up for and Enabling Enhanced Monitoring

To set up for and enable Enhanced Monitoring, take the steps listed following.

Before You Begin

Enhanced Monitoring requires permission to act on your behalf to send OS metric information to CloudWatch Logs. You grant Enhanced Monitoring the required permissions using an AWS Identity and Access Management (IAM) role.

The first time that you enable Enhanced Monitoring in the console, you can select the Default option for the Monitoring Role property to have RDS create the required IAM role. RDS then automatically creates a role named rds-monitoring-role for you, and uses it for the specified DB instance or Read Replica.

You can also create the required role before you enable Enhanced Monitoring, and then specify your new role's name when you enable Enhanced Monitoring. You must create this required role if you enable Enhanced Monitoring using the AWS CLI or the RDS API.

To create the appropriate IAM role to permit Amazon RDS to communicate with the Amazon CloudWatch Logs service on your behalf, take the following steps.

The user that enables Enhanced Monitoring must be granted the PassRole permission. For more information, see Example 2 in Granting a User Permissions to Pass a Role to an AWS Service in the IAM User Guide.

To create an IAM role for Amazon RDS Enhanced Monitoring

Open the IAM Console at https://console.aws.amazon.com.
In the navigation pane, choose Roles.
Choose Create role.
Choose the AWS service tab, and then choose RDS from the list of services.
Choose RDS - Enhanced Monitoring, and then choose Next: Permissions.
Ensure that the Attached permissions policy page shows AmazonRDSEnhancedMonitoringRole, and then choose Next: Tags.
On the Add tags page, choose Next: Review.
For Role Name, enter a name for your role, for example emaccess, and then choose Create role.

Enabling and Disabling Enhanced Monitoring

You can enable Enhanced Monitoring when you create a DB instance or Read Replica, or when you modify a DB instance. If you modify a DB instance to enable Enhanced Monitoring, you don't need to reboot your DB instance for the change to take effect.

You can enable Enhanced Monitoring in the RDS console when you do one of the following actions:

Create a DB Instance – You can enable Enhanced Monitoring in the Configure Advanced Settings page.
Create a Read Replica – You can enable Enhanced Monitoring in the Configure Advanced Settings page.
Modify a DB Instance – You can enable Enhanced Monitoring in the Modify DB Instance page.

To enable Enhanced Monitoring by using the RDS console, scroll to the Monitoring section and do the following:

Choose Enable enhanced monitoring for your DB instance or Read Replica.
Set the Monitoring Role property to the IAM role that you created to permit Amazon RDS to communicate with Amazon CloudWatch Logs for you, or choose Default to have RDS create a role for you named rds-monitoring-role.
Set the Granularity property to the interval, in seconds, between points when metrics are collected for your DB instance or Read Replica. The Granularity property can be set to one of the following values: 1, 5, 10, 15, 30, or 60.

To disable Enhanced Monitoring, choose Disable enhanced monitoring.

Enabling Enhanced Monitoring doesn't require your DB instance to restart.

Note

The fastest that the RDS console refreshes is every 5 seconds. If you set the granularity to 1 second in the RDS console, you still see updated metrics only every 5 seconds. You can retrieve 1-second metric updates by using CloudWatch Logs.

Viewing Enhanced Monitoring

You can view OS metrics reported by Enhanced Monitoring in the RDS console by choosing Enhanced monitoring for Monitoring.

The Enhanced Monitoring page is shown following.

Some DB instances use more than one disk for the DB instance's data storage volume. On those DB instances, the Physical Devices graphs show metrics for each one of the disks. For example, the following graph shows metrics for four disks.

Note

Currently, Physical Devices graphs are not available for Microsoft SQL Server DB instances.

When you are viewing aggregated Disk I/O and File system graphs, the rdsdev device relates to the /rdsdbdata file system, where all database files and logs are stored. The filesystem device relates to the / file system (also known as root), where files related to the operating system are stored.

If the DB instance is a Multi-AZ deployment, you can view the OS metrics for the primary DB instance and its Multi-AZ standby replica. In the Enhanced monitoring view, choose primary to view the OS metrics for the primary DB instance, or choose secondary to view the OS metrics for the standby replica.

Primary and secondary choice for Enhanced Monitoring

For more information about Multi-AZ deployments, see High Availability (Multi-AZ) for Amazon RDS.

Note

Currently, viewing OS metrics for a Multi-AZ standby replica is not supported for MariaDB, Microsoft SQL Server, or PostgreSQL DB instances.

If you want to see details for the processes running on your DB instance, choose OS process list for Monitoring.

The Process List view is shown following.

The Enhanced Monitoring metrics shown in the Process list view are organized as follows:

RDS child processes – Shows a summary of the RDS processes that support the DB instance, for example mysqld for MySQL DB instances. Process threads appear nested beneath the parent process. Process threads show CPU utilization only as other metrics are the same for all threads for the process. The console displays a maximum of 100 processes and threads. The results are a combination of the top CPU consuming and memory consuming processes and threads. If there are more than 50 processes and more than 50 threads, the console displays the top 50 consumers in each category. This display helps you identify which processes are having the greatest impact on performance.
RDS processes – Shows a summary of the resources used by the RDS management agent, diagnostics monitoring processes, and other AWS processes that are required to support RDS DB instances.
OS processes – Shows a summary of the kernel and system processes, which generally have minimal impact on performance.

The items listed for each process are:

VIRT – Displays the virtual size of the process.
RES – Displays the actual physical memory being used by the process.
CPU% – Displays the percentage of the CPU bandwidth consumed by the process.
MEM% – Displays the percentage of the total memory consumed by the process.

The monitoring data that is shown in the RDS console is retrieved from Amazon CloudWatch Logs. You can also retrieve the metrics for a DB instance as a log stream from CloudWatch Logs. For more information, see Viewing Enhanced Monitoring by Using CloudWatch Logs.

Enhanced Monitoring metrics are not returned during the following:

A failover of the DB instance.
Changing the instance class of the DB instance (scale compute).

Enhanced Monitoring metrics are returned during a reboot of a DB instance because only the database engine is rebooted. Metrics for the operating system are still reported.

Viewing Enhanced Monitoring by Using CloudWatch Logs

After you have enabled Enhanced Monitoring for your DB instance, you can view the metrics for your DB instance using CloudWatch Logs, with each log stream representing a single DB instance being monitored. The log stream identifier is the resource identifier (DbiResourceId) for the DB instance.

To view Enhanced Monitoring log data

Open the CloudWatch console at https://console.aws.amazon.com/cloudwatch/.
If necessary, choose the region that your DB instance is in. For more information, see Regions and Endpoints in the Amazon Web Services General Reference.
Choose Logs in the navigation pane.
Choose RDSOSMetrics from the list of log groups.

In a Multi-AZ deployment, log files with -secondary appended to the name are for the Multi-AZ standby replica.
Choose the log stream that you want to view from the list of log streams.

Available OS Metrics

The following tables list the OS metrics available using Amazon CloudWatch Logs.

Metrics for MariaDB, MySQL, Oracle, and PostgreSQL DB instances

Group	Metrics	Description
`General`	`engine`	The database engine for the DB instance.
	`instanceID`	The DB instance identifier.
	`instanceResourceID`	A region-unique, immutable identifier for the DB instance, also used as the log stream identifier.
	`numVCPUs`	The number of virtual CPUs for the DB instance.
	`timestamp`	The time at which the metrics were taken.
	`uptime`	The amount of time that the DB instance has been active.
	`version`	The version of the OS metrics' stream JSON format.
`cpuUtilization`	`guest`	The percentage of CPU in use by guest programs.
	`idle`	The percentage of CPU that is idle.
	`irq`	The percentage of CPU in use by software interrupts.
	`nice`	The percentage of CPU in use by programs running at lowest priority.
	`steal`	The percentage of CPU in use by other virtual machines.
	`system`	The percentage of CPU in use by the kernel.
	`total`	The total percentage of the CPU in use. This value includes the `nice` value.
	`user`	The percentage of CPU in use by user programs.
	`wait`	The percentage of CPU unused while waiting for I/O access.
`diskIO`	`avgQueueLen`	The number of requests waiting in the I/O device's queue.
	`avgReqSz`	The average request size, in kilobytes.
	`await`	The number of milliseconds required to respond to requests, including queue time and service time.
	`device`	The identifier of the disk device in use.
	`readIOsPS`	The number of read operations per second.
	`readKb`	The total number of kilobytes read.
	`readKbPS`	The number of kilobytes read per second.
	`rrqmPS`	The number of merged read requests queued per second.
	`tps`	The number of I/O transactions per second.
	`util`	The percentage of CPU time during which requests were issued.
	`writeIOsPS`	The number of write operations per second.
	`writeKb`	The total number of kilobytes written.
	`writeKbPS`	The number of kilobytes written per second.
	`wrqmPS`	The number of merged write requests queued per second.
`fileSys`	`maxFiles`	The maximum number of files that can be created for the file system.
	`mountPoint`	The path to the file system.
	`name`	The name of the file system.
	`total`	The total number of disk space available for the file system, in kilobytes.
	`used`	The amount of disk space used by files in the file system, in kilobytes.
	`usedFilePercent`	The percentage of available files in use.
	`usedFiles`	The number of files in the file system.
	`usedPercent`	The percentage of the file-system disk space in use.
`loadAverageMinute`	`fifteen`	The number of processes requesting CPU time over the last 15 minutes.
	`five`	The number of processes requesting CPU time over the last 5 minutes.
	`one`	The number of processes requesting CPU time over the last minute.
`memory`	`active`	The amount of assigned memory, in kilobytes.
	`buffers`	The amount of memory used for buffering I/O requests prior to writing to the storage device, in kilobytes.
	`cached`	The amount of memory used for caching file system–based I/O.
	`dirty`	The amount of memory pages in RAM that have been modified but not written to their related data block in storage, in kilobytes.
	`free`	The amount of unassigned memory, in kilobytes.
	`hugePagesFree`	The number of free huge pages. Huge pages are a feature of the Linux kernel.
	`hugePagesRsvd`	The number of committed huge pages.
	`hugePagesSize`	The size for each huge pages unit, in kilobytes.
	`hugePagesSurp`	The number of available surplus huge pages over the total.
	`hugePagesTotal`	The total number of huge pages for the system.
	`inactive`	The amount of least-frequently used memory pages, in kilobytes.
	`mapped`	The total amount of file-system contents that is memory mapped inside a process address space, in kilobytes.
	`pageTables`	The amount of memory used by page tables, in kilobytes.
	`slab`	The amount of reusable kernel data structures, in kilobytes.
	`total`	The total amount of memory, in kilobytes.
	`writeback`	The amount of dirty pages in RAM that are still being written to the backing storage, in kilobytes.
`network`	`interface`	The identifier for the network interface being used for the DB instance.
	`rx`	The number of bytes received per second.
	`tx`	The number of bytes uploaded per second.
`processList`	`cpuUsedPc`	The percentage of CPU used by the process.
	`id`	The identifier of the process.
	`memoryUsedPc`	The amount of memory used by the process, in kilobytes.
	`name`	The name of the process.
	`parentID`	The process identifier for the parent process of the process.
	`rss`	The amount of RAM allocated to the process, in kilobytes.
	`tgid`	The thread group identifier, which is a number representing the process ID to which a thread belongs. This identifier is used to group threads from the same process.
	`VIRT`	The amount of virtual memory allocated to the process, in kilobytes.
`swap`	`swap`	The amount of swap memory available, in kilobytes.
	`swap in`	The amount of memory, in kilobytes, swapped in from disk.
	`swap out`	The amount of memory, in kilobytes, swapped out to disk.
	`free`	The amount of swap memory free, in kilobytes.
	`committed`	The amount of swap memory, in kilobytes, used as cache memory.
`tasks`	`blocked`	The number of tasks that are blocked.
	`running`	The number of tasks that are running.
	`sleeping`	The number of tasks that are sleeping.
	`stopped`	The number of tasks that are stopped.
	`total`	The total number of tasks.
	`zombie`	The number of child tasks that are inactive with an active parent task.

Metrics for Microsoft SQL Server DB instances

Group	Metrics	Description
`General`	`engine`	The database engine for the DB instance.
	`instanceID`	The DB instance identifier.
	`instanceResourceID`	A region-unique, immutable identifier for the DB instance, also used as the log stream identifier.
	`numVCPUs`	The number of virtual CPUs for the DB instance.
	`timestamp`	The time at which the metrics were taken.
	`uptime`	The amount of time that the DB instance has been active.
	`version`	The version of the OS metrics' stream JSON format.
`cpuUtilization`	`idle`	The percentage of CPU that is idle.
	`kern`	The percentage of CPU in use by the kernel.
	`user`	The percentage of CPU in use by user programs.
`disks`	`name`	The identifier for the disk.
	`totalKb`	The total space of the disk, in kilobytes.
	`usedKb`	The amount of space used on the disk, in kilobytes.
	`usedPc`	The percentage of space used on the disk.
	`availKb`	The space available on the disk, in kilobytes.
	`availPc`	The percentage of space available on the disk.
	`rdCountPS`	The number of read operations per second
	`rdBytesPS`	The number of bytes read per second.
	`wrCountPS`	The number of write operations per second.
	`wBytesPS`	The amount of bytes written per second.
`memory`	`commitTotKb`	The amount of pagefile-backed virtual address space in use, that is, the current commit charge. This value is composed of main memory (RAM) and disk (pagefiles).
	`commitLimitKb`	The maximum possible value for the `commitTotKb` metric. This value is the sum of the current pagefile size plus the physical memory available for pageable contents–excluding RAM that is assigned to non-pageable areas.
	`commitPeakKb`	The largest value of the `commitTotKb` metric since the operating system was last started.
	`kernTotKb`	The sum of the memory in the paged and non-paged kernel pools, in kilobytes.
	`kernPagedKb`	The amount of memory in the paged kernel pool, in kilobytes.
	`kernNonpagedKb`	The amount of memory in the non-paged kernel pool, in kilobytes.
	`pageSize`	The size of a page, in bytes.
	`physTotKb`	The amount of physical memory, in kilobytes.
	`physAvailKb`	The amount of available physical memory, in kilobytes.
	`sqlServerTotKb`	The amount of memory committed to Microsoft SQL Server, in kilobytes.
	`sysCacheKb`	The amount of system cache memory, in kilobytes.
`network`	`interface`	The identifier for the network interface being used for the DB instance.
	`rdBytesPS`	The number of bytes received per second.
	`wrBytesPS`	The number of bytes sent per second.
`processList`	`cpuUsedPc`	The percentage of CPU used by the process.
	`memUsedPc`	The percentage of total memory used by the process.
	`name`	The name of the process.
	`pid`	The identifier of the process. This value is not present for processes that are owned by Amazon RDS.
	`ppid`	The process identifier for the parent of this process. This value is only present for child processes.
	`tid`	The thread identifier. This value is only present for threads. The owning process can be identified by using the `pid` value.
	`workingSetKb`	The amount of memory in the private working set plus the amount of memory that is in use by the process and can be shared with other processes, in kilobytes.
	`workingSetPrivKb`	The amount of memory that is in use by a process, but can't be shared with other processes, in kilobytes.
	`workingSetShareableKb`	The amount of memory that is in use by a process and can be shared with other processes, in kilobytes.
	`virtKb`	The amount of virtual address space the process is using, in kilobytes. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages.
`system`	`handles`	The number of handles that the system is using.
	`processes`	The number of processes running on the system.
	`threads`	The number of threads running on the system.

Warning Javascript is disabled or is unavailable in your browser.

To use the AWS Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions.

Document Conventions

« Previous Next »