RDS Enhanced Monitoring & CloudWatch

• RDS provides metrics in real time for the operating system that your database instance runs on.

• You can view the metrics for your database instance using the console, or consume the Enhanced Monitoring JSON output from 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.

• Take note that there are certain differences between CloudWatch and Enhanced Monitoring Metrics:

  • CloudWatch gathers metrics about CPU utilization from the hypervisor for a DB instance.

  • 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 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.

• For example, if you want to closely monitor how the different processes or threads on a DB instance use the CPU, including the percentage of the CPU bandwidth and total memory consumed by each process:

  • You use enhanced monitoring on RDS.

  • You do not use CloudWatch to monitor the CPU Utilization of your database because although it can monitor the CPU Utilization of your database instance, it does not provide the percentage of the CPU bandwidth and total memory consumed by each database process in your RDS instance.

    • CloudWatch gathers metrics about CPU utilization from the hypervisor for a DB instance while RDS Enhanced Monitoring gathers its metrics from an agent on the instance.