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
It would be great to have an option to define how long a service needs to be down before a notification is sent. This would help reduce unnecessary alerts caused by short-lived downtimes, such
Scheduled restarts that briefly take a service
Network hiccups or temporary connectivity
Auto-recovery mechanisms, where a service might restart successfully within a few seconds.
Describe how you would like to see this feature implemented
A configurable grace period or an option to retry X times before alerting would allow users to fine-tune their monitoring setup, ensuring that only persistent outages trigger notifications.
Would this be feasible to implement?
The text was updated successfully, but these errors were encountered:
+1, currently sitting with 402 e-mails from an application that was flapping. The application should also be up for X amount of time before sending repeated alerts.
Describe the feature you would like to see
It would be great to have an option to define how long a service needs to be down before a notification is sent. This would help reduce unnecessary alerts caused by short-lived downtimes, such
Describe how you would like to see this feature implemented
A configurable grace period or an option to retry X times before alerting would allow users to fine-tune their monitoring setup, ensuring that only persistent outages trigger notifications.
Would this be feasible to implement?
The text was updated successfully, but these errors were encountered: