Skip to content
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

Open
gouku opened this issue Nov 28, 2022 · 3 comments
Open

Repeating notifications #379

gouku opened this issue Nov 28, 2022 · 3 comments
Labels
area/alerting Related to alerting feature New feature or request

Comments

@gouku
Copy link

gouku commented Nov 28, 2022

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

@TwiN TwiN added area/alerting Related to alerting feature New feature or request labels Nov 28, 2022
@TwiN
Copy link
Owner

TwiN commented Nov 28, 2022

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.
For instance, pagerduty incidents need an acknowledgement on resolve, so we probably don't want to trigger multiple alerts simultaneously for pagerduty. For Slack, Discord, Teams, Telegram, etc. it shouldn't be an issue.

@TwiN TwiN changed the title feat: repeating notifications? Repeating notifications Feb 5, 2023
@diamonddelt
Copy link

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.

@mxcd
Copy link
Contributor

mxcd commented Mar 9, 2024

From what I can see, #614 is implementing this functionality ready for review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/alerting Related to alerting feature New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants