随后向SNS发出CloudWatch警报通知 [英] Subsequent CloudWatch Alarm notifications to SNS

问题描述

当我使用CloudWatch警报触发AutoScaling操作时，它会反复触发ASG操作。换句话说，随后一组状态为ALARM的N个警报将触发ASG上的N个操作。对于SNS操作，未观察到此行为，而是仅在警报从确定变为警报时才在第一事件中触发。

When I use CloudWatch alarm to trigger an AutoScaling action, it repeatedly trigger the ASG actions. In other words, a subsequent set of N Alarms with state ALARM will trigger N actions on ASG. This behavior was not observed for a SNS action, instead it's triggering only within the 1st event when the Alarm changes from OK to ALARM. Is it possible achieve the same action behavior on SNS similar to ASG?

推荐答案

Amazon CloudWatch警报只会触发Amazon SNS通知吗？当警报 输入处于 ALARM 状态时。也就是说，它仅触发一次，并且仅在从非 ALARM 的状态进入 ALARM 状态时触发。

An Amazon CloudWatch alarm will only trigger an Amazon SNS notification when the alarm enters the ALARM state. That is, it triggers only once, and only when moving from something that isn't ALARM into the ALARM state.

但是，同一CloudWatch警报将继续触发自动扩展策略。

The same CloudWatch alarm, however, will continue to trigger an Auto Scaling Policy.

例如，如果将警报设置为在平均CPU使用率超过80％时触发，则当警报位于 ALARM 状态。扩展政策还具有一个预热期，在此期间将不会执行其他扩展操作（除非定义了多个步骤并且违反了另一个步骤限制）。

For example, if an alarm is set to trigger when average CPU Utilization is above 80%, then the alarm will continue to trigger the Scaling Policy while the alarm is in the ALARM state. The Scaling Policy also has a warmup period, during which no additional scaling actions will take place (unless multiple steps are defined and another step limit has been breached).

上述行为是有意的，不能进行其他配置。

The above behaviours are intentional and cannot be configured differently.

这篇关于随后向SNS发出CloudWatch警报通知的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！