starred/healthchecks

Fork 0

mirror of https://github.com/healthchecks/healthchecks.git synced 2026-04-25 06:55:53 +03:00

[GH-ISSUE #926] Planned Down Time #653

New issue

Closed

opened 2026-02-25 23:43:10 +03:00 by kerem · 5 comments

kerem commented

2026-02-25 23:43:10 +03:00

Owner

Originally created by @TechyChap on GitHub (Dec 11, 2023).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/926

We have an alert which we know should be pinged every hour. But not between the hours of 1am and 3am.
We also have planned outages for certain systems where we know it advance that the healthcheck won't be triggered.

It would be good to be able to add on off and/or recurring "down time" for specific healthchecks so that they don't alert during these times.

Originally created by @TechyChap on GitHub (Dec 11, 2023). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/926 We have an alert which we know should be pinged every hour. But not between the hours of 1am and 3am. We also have planned outages for certain systems where we know it advance that the healthcheck won't be triggered. It would be good to be able to add on off and/or recurring "down time" for specific healthchecks so that they don't alert during these times.

kerem

2026-02-25 23:43:10 +03:00

closed this issue
added the
feature
label

kerem commented

2026-02-25 23:43:10 +03:00

Author

Owner

@hknobbe commented on GitHub (Dec 22, 2023):

Maybe, as a work arround, use the API > Check - Pause/Resume endpoints to pause en resume the checks at the given times?

@hknobbe commented on GitHub (Dec 22, 2023): Maybe, as a work arround, use the API > Check - Pause/Resume endpoints to pause en resume the checks at the given times?

kerem commented

2026-02-25 23:43:10 +03:00

Author

Owner

@ravench commented on GitHub (Jul 8, 2024):

How is this a improvement over specifying the schedule accordingly?
For example:

0 3-23 * * *
3..23:00:00

In my opinion, a planned maintenance would typically not be reoccurring every night, but on certain dates/time ranges.
The feature as such would be useful, tough. (as in "Don't spam me next Saturday from 08:00 to 18:00.")

@ravench commented on GitHub (Jul 8, 2024): How is this a improvement over specifying the schedule accordingly? For example: ```plain 0 3-23 * * * 3..23:00:00 ``` In my opinion, a planned maintenance would typically not be reoccurring every night, but on certain dates/time ranges. The feature as such would be useful, tough. (as in "Don't spam me next Saturday from 08:00 to 18:00.")

kerem commented

2026-02-25 23:43:10 +03:00

Author

Owner

@TechyChap commented on GitHub (Jul 8, 2024):

In this case, we are using the healthchecks to ensure that parcels are being shipped out from the warehouse. They don't expect the workers to be working from 1am to 3am each night as that time is used for inbound goods.

How is this a improvement over specifying the schedule accordingly?

From 3 to 23 doesn't work as we would not get alerted between 11pm and 1am. That would require 2 cron schedules. Although I suppose with some clever use of timezones we could get it to work.

@TechyChap commented on GitHub (Jul 8, 2024): In this case, we are using the healthchecks to ensure that parcels are being shipped out from the warehouse. They don't expect the workers to be working from 1am to 3am each night as that time is used for inbound goods. >How is this a improvement over specifying the schedule accordingly? From 3 to 23 doesn't work as we would not get alerted between 11pm and 1am. That would require 2 cron schedules. Although I suppose with some clever use of timezones we could get it to work.

kerem commented

2026-02-25 23:43:10 +03:00

Author

Owner

@cuu508 commented on GitHub (Jul 8, 2024):

@TechyChap, this would trigger on every round hour except 1AM and 2AM:

0 0,3-23 * * *

@cuu508 commented on GitHub (Jul 8, 2024): @TechyChap, this would trigger on every round hour except 1AM and 2AM: 0 0,3-23 * * *

kerem commented

2026-02-25 23:43:10 +03:00

Author

Owner

@cuu508 commented on GitHub (Nov 21, 2025):

For irregular schedules, use cron or oncalendar schedules.

For planned maintenance, pause the checks before, and resume them afterwards.

I'm not planning to add functionality to schedule maintenance windows in advance – I would like to keep Healthchecks simple and lean, and this functionality is little too niche for me.

@cuu508 commented on GitHub (Nov 21, 2025): For irregular schedules, use cron or oncalendar schedules. For planned maintenance, pause the checks before, and resume them afterwards. I'm not planning to add functionality to schedule maintenance windows in advance – I would like to keep Healthchecks simple and lean, and this functionality is little too niche for me.