Avoiding INSUFFICIENT_DATA CloudWatch SNS Notifications

I have an SNS topic that is published whenever a SES message appears. I have a CloudWatch alarm that starts when the notification threshold crosses in the last hour.

In practice, bounces are rare, and since SNS notifications are only sent when email is scanned, the alarm spends almost all of its time in the state INSUFFICIENT_DATA.

Ideally, I would like the absence of SNS notifications to be considered a null value. In other monitoring systems (for example, graphite / graphane) this is considered "zero".

Is there a way to handle (no) notifications in this way and leave the alarm out of data inadequacy?

+4
source share
1 answer

Amazon SNS does not send metric data to CloudWatch when the value is zero. This leads to INSUFFICIENT_DATAalarms in which emails are not sent. However, your alarm should work unchanged.

A message INSUFFICIENT_DATAarises from two situations:

  • An alarm did not exist for the measurement period (for example, an alarm that calculates the total value over a 1-hour period must exist for at least 1 hour).
  • No data for a certain period of time

, , OK, ALARM.

, INSUFFICIENT_DATA , OK. ( INSUFFICIENT DATA!)

, , SUM, AVERAGE, . , SUM , AVERAGE .

+4

All Articles