Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Suppress cloudwatch alerts when the state changes from INSUFFICIENT_DATA to OK #397

Open
veldotshine opened this issue Apr 9, 2020 · 0 comments

Comments

@veldotshine
Copy link
Collaborator

veldotshine commented Apr 9, 2020

Is your feature request related to a problem? Please describe.
Cloudwatch alarms are created part of fullset stack. The alarms are configured to trigger for ALARM and OK State. The alarm state is set to INSUFFICIENT_DATA when an cloudwatch alarm is created, and then it moves to OK state once it collects the data point in the evaluation range. During this period, since the state changes from INSUFFICIENT_DATA to OK the alarms triggers SNS notification. This creates a bunch of alerts whenever a new full set is created.

Describe the solution you'd like
Inorder to avoid the alerts being triggered during a new full set creation.,

  • A lambda function can be added to alarms and it can trigger the SNS alert for OK state based on the old_state of the alarm.
    • i.e Ignore the alert, if the old_state value is INSUFFICIENT_DATA.
    • Trigger the SNS notification887, if the old_state value is ALARM.

Additional context
This is only an overhead when SNS notifications are integrated with Opsgenie/any other alert system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant