You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: