#126

New issue

Closed

opened 2026-02-25 23:41:16 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @danemacmillan on GitHub (Jul 13, 2018).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/180

Right now the default seems to be 3s for the /checks/status/ endpoint. I realize this will add greater stress to the hosted version, so perhaps include it on one of the paid plans. I'm paying for Standard right now.

I only recently needed this as I have some jobs that run sub-minute, so seeing the refresh more configurable would be nice.

Great service!

Originally created by @danemacmillan on GitHub (Jul 13, 2018). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/180 Right now the default seems to be `3s` for the `/checks/status/` endpoint. I realize this will add greater stress to the hosted version, so perhaps include it on one of the paid plans. I'm paying for Standard right now. I only recently needed this as I have some jobs that run sub-minute, so seeing the refresh more configurable would be nice. Great service!

kerem

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

closed this issue
added the
feature
label

kerem commented

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

Author

Owner

@cuu508 commented on GitHub (Jul 24, 2018):

Thanks for the idea!

The added load would be manageable -- as long as we're careful not to run 1s refresh indefinitely when somebody has a healthchecks.io tab open and goes on a vacation (and similar scenarios).

I'm guessing, with sub-minute pings you often see "XX seconds ago" in the last ping column, and the value is not steadily going up every second, but jumping by 3 every 3 seconds. Do you just want the counter to go up every second so it looks more smooth and realtime, or do you in fact need the extra precision?

If it's the former, we could also cheat a bit and extrapolate the values on client side, keeping the 3 second refresh interval.

@cuu508 commented on GitHub (Jul 24, 2018): Thanks for the idea! The added load would be manageable -- as long as we're careful not to run 1s refresh indefinitely when somebody has a healthchecks.io tab open and goes on a vacation (and similar scenarios). I'm guessing, with sub-minute pings you often see "XX seconds ago" in the last ping column, and the value is not steadily going up every second, but jumping by 3 every 3 seconds. Do you just want the counter to go up every second so it looks more smooth and realtime, or do you in fact need the extra precision? If it's the former, we could also cheat a bit and extrapolate the values on client side, keeping the 3 second refresh interval.

kerem commented

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

Author

Owner

@danemacmillan commented on GitHub (Aug 1, 2018):

I would definitely want to have precision over the appearance. I actually think the last ping time should always just reflect that, and not fill in the gaps, so I'm against the idea of 1s updates just to look smooth.

I'd like to have it customizable, so, for example, if this were implemented, I would see the default refresh interval you set as 3s, and then I could select another option, like 1s or 5s or 10s, etc. This is why I would say push it onto a paid plan, specifically the low refresh times like 1s.

I have to admit, I have no immediate need for it. The moment I saw the 3s refresh, the thought popped into my head. It was a knobs-and-dials moment for me. I recently added three checks that occur every 30 seconds, and I know as I integrate more checks into operations, I'll be adding more sub-minute checks.

@danemacmillan commented on GitHub (Aug 1, 2018): I would definitely want to have precision over the appearance. I actually think the last ping time should always just reflect that, and not fill in the gaps, so I'm against the idea of 1s updates just to look smooth. I'd like to have it customizable, so, for example, if this were implemented, I would see the default refresh interval you set as `3s`, and then I could select another option, like `1s` or `5s` or `10s`, etc. This is why I would say push it onto a paid plan, specifically the low refresh times like `1s`. I have to admit, I have no immediate need for it. The moment I saw the `3s` refresh, the thought popped into my head. It was a knobs-and-dials moment for me. I recently added three checks that occur every 30 seconds, and I know as I integrate more checks into operations, I'll be adding more sub-minute checks.

kerem commented

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

Author

Owner

@cuu508 commented on GitHub (Apr 29, 2022):

Closing – I'll stick with a simple, fixed 3s polling frequency. Knobs and dials have complexity cost, which I'm trying to avoid very much ;-)

@cuu508 commented on GitHub (Apr 29, 2022): Closing – I'll stick with a simple, fixed 3s polling frequency. Knobs and dials have complexity cost, which I'm trying to avoid very much ;-)