简体   繁体   English

随后向SNS发出CloudWatch警报通知

[英]Subsequent CloudWatch Alarm notifications to SNS

When I use CloudWatch alarm to trigger an AutoScaling action, it repeatedly trigger the ASG actions. 当我使用CloudWatch警报触发AutoScaling操作时,它会反复触发ASG操作。 In other words, a subsequent set of N Alarms with state ALARM will trigger N actions on ASG. 换句话说,随后一组状态为ALARM的N个警报将触发ASG上的N个操作。 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. 对于SNS操作,未观察到此行为,而是仅在警报从“确定”变为“警报”时才在第一事件中触发。 Is it possible achieve the same action behavior on SNS similar to ASG? 是否可以在SNS上实现与ASG类似的相同动作行为?

An Amazon CloudWatch alarm will only trigger an Amazon SNS notification when the alarm enters the ALARM state . 仅当警报进入 ALARM状态时,Amazon CloudWatch警报才会触发Amazon SNS通知。 That is, it triggers only once, and only when moving from something that isn't ALARM into the ALARM state. 也就是说,它会触发只有一次,只有从东西是不动的时候ALARM进入ALARM状态。

The same CloudWatch alarm, however, will continue to trigger an Auto Scaling Policy. 但是,相同的CloudWatch警报将继续触发 Auto Scaling策略。

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. 例如,如果将警报设置为在平均CPU使用率超过80%时触发,那么当警报处于ALARM状态时,警报将继续触发扩展策略。 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. 以上行为是故意的,不能进行其他配置。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM