mirror of
https://github.com/healthchecks/healthchecks.git
synced 2026-04-25 23:15:49 +03:00
[GH-ISSUE #209] Different Grace Time for each Notification Method #153
Labels
No labels
bug
bug
bug
feature
good-first-issue
new integration
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/healthchecks#153
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Eh2406 on GitHub (Dec 12, 2018).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/209
Thanks for making healthchecks! It is saving us at work!
We have a daily backup script that (now) has a ping to a check. It is set up to notify me and my boss. Inpractice it is not a big deal if we miss a day, so it is overkill for my boss to be bothered unless it is more then 2 days late.
My current solution is to set up 2 checks, one with a 30 minute grace time for me, and a second with a 1 day grace time for my boss. With the script pinging both checks. It would be easier to maintain if I could override the grace time on a per notification bases.
Thoughts?
@cuu508 commented on GitHub (Dec 14, 2018):
I understand the use case, and it makes sense, but it would require major changes to support in Healthchecks.
Using two checks with different grace times is a clever trick! Another option would be to offload this task to an incident management system, and configure the escalation policy there. We already have integrations for PagerDuty, OpsGenie, VictorOps, PagerTree. Happy to add others.