AWS AmazonCloudWatch documentation change
Summary
Added 'Log Alarm support' column to alarm actions table and updated support details. Added explanation of notification content differences for log alarms.
Security assessment
Changes only expand feature documentation about log alarm support and notification formatting. No security vulnerabilities, configurations, or features are addressed.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/alarm-actions.md b/AmazonCloudWatch/latest/monitoring/alarm-actions.md index 366f00d0e..bcf6ff168 100644 --- a//AmazonCloudWatch/latest/monitoring/alarm-actions.md +++ b//AmazonCloudWatch/latest/monitoring/alarm-actions.md @@ -38,9 +38,11 @@ The following table shows the actions executed for alarms along with their behav -Action Type | Metrics Insights Multiple Time Series Alarm support | PromQL Alarm support | More Information ----|---|---|--- -SNS notifications | Contributor Level | Contributor Level | [Amazon SNS event destinations](https://docs.aws.amazon.com/sns/latest/dg/sns-event-destinations.html) -EC2 actions (stop, terminate, reboot, recover) | Not supported | Not supported | [Stop, terminate, reboot, or recover an EC2 instance](./UsingAlarmActions.html) -Auto Scaling actions | Not supported | Not supported | [Step and simple scaling policies for Amazon EC2 Auto Scaling](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-scaling-simple-step.html) -Systems Manager OpsItem creation | Alarm Level | Not supported | [Configure CloudWatch alarms to create OpsItems](https://docs.aws.amazon.com/systems-manager/latest/userguide/OpsCenter-create-OpsItems-from-CloudWatch-Alarms.html) -Systems Manager Incident Manager incidents | Alarm Level | Not supported | [Creating incidents automatically with CloudWatch alarms](https://docs.aws.amazon.com/incident-manager/latest/userguide/incident-creation.html#incident-tracking-auto-alarms) -Lambda function invocation | Contributor Level | Contributor Level | [Invoke a Lambda function from an alarm](./alarms-and-actions-Lambda.html) -CloudWatch investigations investigation | Alarm Level | Not supported | [Start a CloudWatch investigations from an alarm](./Start-Investigation-Alarm.html) +Action Type | Metrics Insights Multiple Time Series Alarm support | PromQL Alarm support | Log Alarm support | More Information +---|---|---|---|--- +SNS notifications | Contributor Level | Contributor Level | Contributor Level | [Amazon SNS event destinations](https://docs.aws.amazon.com/sns/latest/dg/sns-event-destinations.html) +EC2 actions (stop, terminate, reboot, recover) | Not supported | Not supported | Not supported | [Stop, terminate, reboot, or recover an EC2 instance](./UsingAlarmActions.html) +Auto Scaling actions | Not supported | Alarm Level1 | Not supported | [Step and simple scaling policies for Amazon EC2 Auto Scaling](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-scaling-simple-step.html) +Systems Manager OpsItem creation | Alarm Level | Not supported | Alarm Level | [Configure CloudWatch alarms to create OpsItems](https://docs.aws.amazon.com/systems-manager/latest/userguide/OpsCenter-create-OpsItems-from-CloudWatch-Alarms.html) +Systems Manager Incident Manager incidents | Alarm Level | Not supported | Not supported | [Creating incidents automatically with CloudWatch alarms](https://docs.aws.amazon.com/incident-manager/latest/userguide/incident-creation.html#incident-tracking-auto-alarms) +Lambda function invocation | Contributor Level | Contributor Level | Contributor Level | [Invoke a Lambda function from an alarm](./alarms-and-actions-Lambda.html) +CloudWatch investigations investigation | Alarm Level | Not supported | Not supported | [Start a CloudWatch investigations from an alarm](./Start-Investigation-Alarm.html) + +1 PromQL alarms support only Application Auto Scaling actions. @@ -55,0 +58,4 @@ The content of alarm notifications differs depending on the alarm type: + * Log alarms without contributors (single-value) include both a state reason and detailed state reason data, showing the query results evaluated. + + * Log alarms with contributors (using a `BY` clause) provide a simplified state reason for each contributor, without the detailed state reason data block. +