到 SNS 的后续 CloudWatch 警报通知 [英] Subsequent CloudWatch Alarm notifications to SNS

问题描述

当我使用 CloudWatch 警报触发 AutoScaling 操作时，它会重复触发 ASG 操作.换句话说，具有 ALARM 状态的一组后续 N 个警报将在 ASG 上触发 N 个动作.对于 SNS 操作未观察到此行为，而是仅在警报从 OK 变为 ALARM 时在第一个事件内触发.是否有可能在 SNS 上实现类似 ASG 的相同动作行为?

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 警报只会在警报进入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 警报将继续触发 Auto Scaling 策略.

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

例如，如果警报设置为在平均 CPU 使用率高于 80% 时触发，则警报将在警报处于 ALARM 状态时继续触发 Scaling Policy.扩展策略还有一个预热期，在此期间不会发生额外的扩展操作(除非定义了多个步骤并且违反了另一个步骤限制).

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屋！