Fixes a set of alarms that don't work for a couple reasons:
Too many evaluation periods to likely ever satisfy
Incorrectly access the Constants resource attributes
This PR fixes the above, and switches the style to match the 500's alarm:
Use a single evaluation period
Use GreaterThanThreshold
In the modified alarms here, the alarm is considered existential: if the error occurs, then set off the alarm. Re: Multiple evaluation periods, I think only in a self-healing scenario (like the actuals falling behind or forecasts slow down a bit) would we want to ignore the error metrics for a single evaluation period. These alarms imply something has gone wrong that needs outside intervention.
Fixes a set of alarms that don't work for a couple reasons:
Constantsresource attributesThis PR fixes the above, and switches the style to match the 500's alarm:
GreaterThanThresholdIn the modified alarms here, the alarm is considered existential: if the error occurs, then set off the alarm. Re: Multiple evaluation periods, I think only in a self-healing scenario (like the actuals falling behind or forecasts slow down a bit) would we want to ignore the error metrics for a single evaluation period. These alarms imply something has gone wrong that needs outside intervention.