[GH-ISSUE #279] Report how many checks were missed #208

New issue

Open

opened 2026-02-25 23:41:36 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @jungle-boogie on GitHub (Aug 21, 2019).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/279

Hello,

Thanks for healthchecks.io and open sourcing your project. Keep up the great work.

When I receive a notification that a check is up on pushover it states this:

The check "pine64" received a ping and is now UP.

All the other checks are up.

I think the email notification is also very similar. I was wondering if you could report how many checks were missed? If I have a 15 minute trigger and I miss a whole hour, I would see something like this:

The check "pine64" received a ping and is now UP.
Four previous checks were missed by "pine64"
All the other checks are up.

Would this be a possibility?

Thanks!

Originally created by @jungle-boogie on GitHub (Aug 21, 2019). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/279 Hello, Thanks for healthchecks.io and open sourcing your project. Keep up the great work. When I receive a notification that a check is up on pushover it states this: ``` The check "pine64" received a ping and is now UP. All the other checks are up. ``` I think the email notification is also very similar. I was wondering if you could report how many checks were missed? If I have a 15 minute trigger and I miss a whole hour, I would see something like this: ``` The check "pine64" received a ping and is now UP. Four previous checks were missed by "pine64" All the other checks are up. ``` Would this be a possibility? Thanks!

kerem added the

feature

label

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

kerem commented

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

Author

Owner

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

Calculating how many checkins were missed has a few complications:

for cron and oncalendar schedules we would need to replay and count the missed checkin times
users can edit check schedules at any time which would throw off the number of missed checkins

We could look into calculating and showing the amount of incurred downtime:

The check "pine64" received a ping and is now UP.
The downtime lasted for 5h 15min.

@cuu508 commented on GitHub (Nov 19, 2025): Calculating how many checkins were missed has a few complications: * for cron and oncalendar schedules we would need to replay and count the missed checkin times * users can edit check schedules at any time which would throw off the number of missed checkins We could look into calculating and showing the amount of incurred downtime: ``` The check "pine64" received a ping and is now UP. The downtime lasted for 5h 15min. ```