[GH-ISSUE #451] suggestion: snooze mode #340

New issue

Open

opened 2026-02-25 23:42:06 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 23:42:06 +03:00

Owner

Originally created by @piramiday on GitHub (Nov 18, 2020).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/451

it would be useful to have a "snooze" button for a specific check/project, possibly curlable itself.

for example, if I reboot a server I know I will have lots of checks suddenly failing -- e.g. the fast pings that take ~10 secs and are performed every ~5 mins or so, or even the more important checks if they are supposed to run at 9:00 and I reboot at 8:55.
with a "snooze" button one could signal to HealthChecks that any failure in the next, say, ~20 mins is expected and should be temporarily disabled.
that would temporarily silence emails and/or other integrations while the server reboots, or the user plays around with a script, and so on.

e.g. curl https://hc-ping.com/xxxx-yyyy-zzzz-wwww/snooze/20 for 20 mins.

if this is not a good idea, feel free to close the issue! thanks.

Originally created by @piramiday on GitHub (Nov 18, 2020). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/451 it would be useful to have a "snooze" button for a specific check/project, possibly `curl`able itself. for example, if I reboot a server I know I will have lots of checks suddenly failing -- e.g. the fast pings that take ~10 secs and are performed every ~5 mins or so, or even the more important checks if they are supposed to run at 9:00 and I reboot at 8:55. with a "snooze" button one could signal to HealthChecks that any failure in the next, say, ~20 mins is expected and should be temporarily disabled. that would temporarily silence emails and/or other integrations while the server reboots, or the user plays around with a script, and so on. e.g. `curl https://hc-ping.com/xxxx-yyyy-zzzz-wwww/snooze/20` for 20 mins. if this is not a good idea, feel free to close the issue! thanks.

kerem added the

feature

label

2026-02-25 23:42:06 +03:00

kerem commented

2026-02-25 23:42:06 +03:00

Author

Owner

@nbvcxz commented on GitHub (Feb 8, 2021):

There is also another idea to get quite same result: see https://github.com/healthchecks/healthchecks/issues/316. That would be the way to pause unwanted checks. There is one drawback of this method: there can ba a moment when child sensor is expected to ping before parent, but it can be solved with setting higher grace periods for children.

@nbvcxz commented on GitHub (Feb 8, 2021): There is also another idea to get quite same result: see https://github.com/healthchecks/healthchecks/issues/316. That would be the way to pause unwanted checks. There is one drawback of this method: there can ba a moment when child sensor is expected to ping before parent, but it can be solved with setting higher grace periods for children.

kerem commented

2026-02-25 23:42:06 +03:00

Author

Owner

@csaftoiu commented on GitHub (Jan 19, 2022):

I want to second this request! It'd be very helpful for our use cases.

@csaftoiu commented on GitHub (Jan 19, 2022): I want to second this request! It'd be very helpful for our use cases.

kerem commented

2026-02-25 23:42:06 +03:00

Author

Owner

@TheCataliasTNT2k commented on GitHub (Oct 26, 2022):

+1 would be great to just silence a whole project for a specific time or permanently (and unsilence it manually when I want it). Would be great for updates and reboots
If a check goes down during that time, and stays down after the reactivation of the project, you should get a notification nevertheless...

@TheCataliasTNT2k commented on GitHub (Oct 26, 2022): +1 would be great to just silence a whole project for a specific time or permanently (and unsilence it manually when I want it). Would be great for updates and reboots If a check goes down during that time, and stays down after the reactivation of the project, you should get a notification nevertheless...

kerem commented

2026-02-25 23:42:06 +03:00

Author

Owner

@horschi commented on GitHub (Aug 14, 2025):

+1 on the curl: Being able to snooze via a HTTP call would allow to integrate it into automation.

@horschi commented on GitHub (Aug 14, 2025): +1 on the curl: Being able to snooze via a HTTP call would allow to integrate it into automation.

kerem referenced this issue

2026-02-25 23:44:11 +03:00

[PR #340] [MERGED] [Snyk] Security upgrade django from 3.0.3 to 3.0.4 #933