From 51e47a5caaacbfa01cd2b99cceb45565d27346f3 Mon Sep 17 00:00:00 2001 From: Daniel Hagan Date: Mon, 28 Aug 2023 10:22:16 -0400 Subject: [PATCH] Fix formatting in rds-and-aurora.md --- docs/en/guides/databases/rds-and-aurora.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/en/guides/databases/rds-and-aurora.md b/docs/en/guides/databases/rds-and-aurora.md index ec459a74..29855c3e 100644 --- a/docs/en/guides/databases/rds-and-aurora.md +++ b/docs/en/guides/databases/rds-and-aurora.md @@ -95,11 +95,12 @@ RDS delivers the metrics from Enhanced Monitoring into your Amazon CloudWatch Lo ![db_enhanced_monitoring_loggroup.png](../../images/db_enhanced_monitoring_loggroup.png) Enhanced monitoring also include the OS level process list. Currently, Enhanced Monitoring is available for the following database engines: -*MariaDB -*Microsoft SQL Server -*MySQL -*Oracle -*PostgreSQL + +* MariaDB +* Microsoft SQL Server +* MySQL +* Oracle +* PostgreSQL **Different between CloudWatch and Enhanced Monitoring** CloudWatch gathers metrics about CPU utilization from the hypervisor for a DB instance. In contrast, Enhanced Monitoring gathers its metrics from an agent on the DB instance. A hypervisor creates and runs virtual machines (VMs). Using a hypervisor, an instance can support multiple guest VMs by virtually sharing memory and CPU. You might find differences between the CloudWatch and Enhanced Monitoring measurements, because the hypervisor layer performs a small amount of work. The differences can be greater if your DB instances use smaller instance classes. In this scenario, more virtual machines (VMs) are probably managed by the hypervisor layer on a single physical instance.