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

Should the CloudWatch alarm's Statistic be set to "Maximum"? #1

Open
kjhosein opened this issue Nov 20, 2017 · 1 comment
Open

Should the CloudWatch alarm's Statistic be set to "Maximum"? #1

kjhosein opened this issue Nov 20, 2017 · 1 comment

Comments

@kjhosein
Copy link

Hi there,

In the CloudWatch alarm, the Statistic is set to "Minimum" and is being evaluated over 3 periods. Let's say the System Status Check came back as 1, 0, then 1 (fail, pass, fail), then with Statistic set to "Minimum", the auto-recover action won't be triggered (Threshold >= 1). Now this may be what you're going for, but personally I'd rather the action be triggered in this scenario, so I'd set the Statistic to Maximum.

Please let me know if my logic and/or understanding of CW is incorrect.
Thanks!

-- Khalid

@cxmcc
Copy link
Owner

cxmcc commented Feb 23, 2018

Hi @kjhosein, Yes. My intention was to avoid triggering actions because of temporary failure of System Status Check. This will trigger a recover after 3 consecutive datapoints of system_status_check = 0 It's always up to the owner to decide which approach to take based on the sensitivity of the system.
Another useful option is treat_missing_data of the cloudwatch alarm, user can either ignore or treat as breaching or notBreaching based on the risk analysis.

Thanks.

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

2 participants