[GH-ISSUE #694] Additional schedule element #499

New issue

Closed

opened 2026-02-25 23:42:41 +03:00 by kerem · 2 comments

kerem commented

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

Owner

Originally created by @DarrenPIngram on GitHub (Aug 12, 2022).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/694

For a script that runs (for example) between 1900-0500 UTC, could there be an additional monitoring element to say the script runs only between these times (so if it was running hourly between these times, Healthcheck would not say at 1200 UTC that "Houston, we have a problem"?

Originally created by @DarrenPIngram on GitHub (Aug 12, 2022). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/694 For a script that runs (for example) between 1900-0500 UTC, could there be an additional monitoring element to say the script runs only between these times (so if it was running hourly between these times, Healthcheck would not say at 1200 UTC that "Houston, we have a problem"?

kerem closed this issue

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

kerem commented

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

Author

Owner

@cuu508 commented on GitHub (Aug 16, 2022):

Perhaps the cron schedule would work here?

0 19-23,0-4 * * * says: expect a ping at the start of every hour, from 19:00 until 05:00 (exclusive).

@cuu508 commented on GitHub (Aug 16, 2022): Perhaps the cron schedule would work here? ![image](https://user-images.githubusercontent.com/661859/184885358-430df370-7ec9-404b-9f4c-b0dbb59088d1.png) `0 19-23,0-4 * * *` says: expect a ping at the start of every hour, from 19:00 until 05:00 (exclusive).

kerem commented

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

Author

Owner

@DarrenPIngram commented on GitHub (Aug 16, 2022):

Ah, thank you. I entirely did not see or appreciate that option there. I
guess I was focussed on the first screen, thinking it might be in the
available options. Thank you for the nudge.

On Tue, 16 Aug 2022 at 16:00, Pēteris Caune @.***>
wrote:

Perhaps the cron schedule would work here?

[image: image]
https://user-images.githubusercontent.com/661859/184885358-430df370-7ec9-404b-9f4c-b0dbb59088d1.png

0 19-23,0-4 * * * says: expect a ping at the start of every hour, from
19:00 until 05:00 (exclusive).

—
Reply to this email directly, view it on GitHub
https://github.com/healthchecks/healthchecks/issues/694#issuecomment-1216605866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABV5MAB5BWKPKAKKKBKTMVLVZOGGVANCNFSM56LUXBAQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

@DarrenPIngram commented on GitHub (Aug 16, 2022): Ah, thank you. I entirely did not see or appreciate that option there. I guess I was focussed on the first screen, thinking it might be in the available options. Thank you for the nudge. On Tue, 16 Aug 2022 at 16:00, Pēteris Caune ***@***.***> wrote: > Perhaps the cron schedule would work here? > > [image: image] > <https://user-images.githubusercontent.com/661859/184885358-430df370-7ec9-404b-9f4c-b0dbb59088d1.png> > > 0 19-23,0-4 * * * says: expect a ping at the start of every hour, from > 19:00 until 05:00 (exclusive). > > — > Reply to this email directly, view it on GitHub > <https://github.com/healthchecks/healthchecks/issues/694#issuecomment-1216605866>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABV5MAB5BWKPKAKKKBKTMVLVZOGGVANCNFSM56LUXBAQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >