-
-
Notifications
You must be signed in to change notification settings - Fork 451
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
Repeating notifications #379
Comments
Sounds like a good idea! Something like this: alerts:
- type: slack
enabled: true
description: "healthcheck failed 3 times in a row"
send-on-resolved: true
repeating: true That said, not all alerting providers should allow this. |
Bumping this because we'd also be interested in having this feature, particularly for the MS Teams alerting hooks. We already use send-on-resolved, but if a service was down for 6+ days and the small team missed the initial message sent to a noisy MS Teams channel, it's easy to miss or forget unless it periodically reminds you it is still failing. |
From what I can see, #614 is implementing this functionality ready for review |
I want this! |
Describe the feature request
Ability to send repeated notifications every x min/hr if the endpoint is still offline/dead.
Why do you personally want this feature to be implemented?
We now had over 300 nodes monitoring via Gatus and we received the notifications via Slack and Telegram. One scenario is when some nodes are offline during the weekend. We always forget to fix them in the next workday.
I've tried some other services and seems like it's a common feature to alert repeatedly if something still goes wrong.
How long have you been using this project?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: