If the value for “fatigue_check/occurrences” is set to 3, the alert behavior should follow this logic:
- Critical Alert: A critical alert will be triggered only after 3 consecutive event failures. This means the system will not raise a critical alert on the first or second failure but will wait until the third failure to generate the alert.
- Resolved Alert: A resolved alert should be triggered only when the most recent event is successful, and all the preceding events (within the history) were failures for at least the last 3 consecutive events. This ensures that a resolve alert is raised only after the issue was persistent for 3 or more consecutive failures and then successfully resolved.
Hope this helps
