AWS prescriptive-guidance documentation change
Summary
Updated documentation links, image paths, and minor text edits for clarity. Changed 'graph' to 'diagram', adjusted formatting for alarm types, and fixed section references.
Security assessment
Changes involve broken link fixes, image path updates, and minor wording improvements without introducing new security content or addressing vulnerabilities. Monitoring documentation exists but changes don't alter security posture or reference security incidents.
Diff
diff --git a/prescriptive-guidance/latest/amazon-rds-monitoring-alerting/cloudwatch-alarms.md b/prescriptive-guidance/latest/amazon-rds-monitoring-alerting/cloudwatch-alarms.md index dc9ed4d09..7c59c1977 100644 --- a//prescriptive-guidance/latest/amazon-rds-monitoring-alerting/cloudwatch-alarms.md +++ b//prescriptive-guidance/latest/amazon-rds-monitoring-alerting/cloudwatch-alarms.md @@ -9 +9 @@ -When you operate your Amazon RDS DB instances, you want to monitor and generate alerts on different kinds of metrics, events, and traces. For MySQL and MariaDB databases, the critical sources of information are [DB instance metrics](./db-instance-monitoring.html), [OS metrics](./os-monitoring.html), [events, logs, and audit trails](./events-logs-audit.html). We recommend that you use [CloudWatch alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html) to watch a single metric over a time period that you specify. +When you operate your Amazon RDS DB instances, you want to monitor and generate alerts on different kinds of metrics, events, and traces. For MySQL and MariaDB databases, the critical sources of information are [DB instance metrics](./database-instance-monitoring.html), [OS metrics](./os-monitoring.html), [events, logs, and audit trails](./events-logs-audit.html). We recommend that you use [CloudWatch alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html) to watch a single metric over a time period that you specify. @@ -13 +13 @@ The following example illustrates how you can set an alarm that watches the `CPU - + @@ -15 +15 @@ The following example illustrates how you can set an alarm that watches the `CPU -This means that the alarm goes into the `ALARM` state if any of your databases experiences a high CPU utilization (over 80 percent) for 5 minutes or more. The alarm remains in the `OK` state if the CPU occasionally bursts to over 80 percent utilization for a short period of time, and then drops again below the threshold. The following graph illustrates this logic. +This means that the alarm goes into the `ALARM` state if any of your databases experiences a high CPU utilization (over 80 percent) for 5 minutes or more. The alarm remains in the `OK` state if the CPU occasionally bursts to over 80 percent utilization for a short period of time, and then drops again below the threshold. The following diagram illustrates this logic. @@ -17 +17 @@ This means that the alarm goes into the `ALARM` state if any of your databases e - + @@ -19 +19 @@ This means that the alarm goes into the `ALARM` state if any of your databases e -CloudWatch alarms support metric and composite alarms. +CloudWatch alarms support _metric_ and _composite_ alarms. @@ -21 +21 @@ CloudWatch alarms support metric and composite alarms. - * A _metric alarm_ watches a single CloudWatch metric and can perform mathematical expressions on the metric. A metric alarm can send Amazon SNS messages, which, in turn, can take one or more actions based on the value of the metric relative to a given threshold over a number of time periods. + * A metric alarm watches a single CloudWatch metric and can perform mathematical expressions on the metric. A metric alarm can send Amazon SNS messages, which, in turn, can take one or more actions based on the value of the metric relative to a given threshold over a number of time periods. @@ -23 +23 @@ CloudWatch alarms support metric and composite alarms. - * A _composite alarm_ is based on a rule expression, which evaluates the states of multiple alarms and goes into the `ALARM` state only if all conditions of the rule are met. Composite alarms are typically used to reduce the number of unnecessary alerts. For example, you might have a composite alarm that contains several metric alarms that are configured never to take actions. The composite alarm would send an alert when all the individual metric alarms in the composite are already in the `ALARM` + * A composite alarm is based on a rule expression, which evaluates the states of multiple alarms and goes into the `ALARM` state only if all conditions of the rule are met. Composite alarms are typically used to reduce the number of unnecessary alerts. For example, you might have a composite alarm that contains several metric alarms that are configured never to take actions. The composite alarm would send an alert when all the individual metric alarms in the composite are already in the `ALARM` @@ -28 +28 @@ CloudWatch alarms support metric and composite alarms. -CloudWatch alarms can watch only CloudWatch metrics. If you want to create an alarm based on the error, slow query, or general logs, you must create CloudWatch metrics from the logs. You can accomplish that as discussed earlier in the [OS monitoring](./os-monitoring.html) and [Events, logs, and audit trails](./events-logs-audit.html) sections, by using filters to [create metrics from log events](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/MonitoringLogData.html). Similarly, to alert on Enhanced Monitoring metrics, you must create metric filters in CloudWatch from CloudWatch Logs. +CloudWatch alarms can watch only CloudWatch metrics. If you want to create an alarm based on the error, slow query, or general logs, you must create CloudWatch metrics from the logs. You can accomplish that as discussed earlier in the [OS](./os-monitoring.html) monitoring and [Events, logs, and audit trails](./events-logs-audit.html) sections, by using filters to [create metrics from log events](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/MonitoringLogData.html). Similarly, to alert on Enhanced Monitoring metrics, you must create metric filters in CloudWatch from CloudWatch Logs.