[GH-ISSUE #151] Allow to submit a "fail" ping #103

Closed
opened 2026-02-25 23:41:12 +03:00 by kerem · 5 comments
Owner

Originally created by @pladen on GitHub (Jan 29, 2018).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/151

It would be great to add the option to submit a "fail" status for a ping
In my use case we run quite a long daily script. I want to know if it runs and if everything is ok.

Cronalarm.com has such a feature. It allows to also submit a short text message like "error occurred at step X"

From API point of view it can be like 👍

curl https://hchk.io/9e525010-64ba-42ea-91aa-db5c7b7598b4/fail

Optional text message can be submit via POST data

Regards

Originally created by @pladen on GitHub (Jan 29, 2018). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/151 It would be great to add the option to submit a "fail" status for a ping In my use case we run quite a long daily script. I want to know if it runs and if everything is ok. Cronalarm.com has such a feature. It allows to also submit a short text message like "error occurred at step X" From API point of view it can be like 👍 ``` curl https://hchk.io/9e525010-64ba-42ea-91aa-db5c7b7598b4/fail ``` Optional text message can be submit via POST data Regards
kerem closed this issue 2026-02-25 23:41:12 +03:00
Author
Owner

@mlaitinen commented on GitHub (May 16, 2018):

How this would work if the "regular" ping overrides the failed status on the next run? My point:

10:00 OK (green light)
10:05 OK (green light)
10:10 OK (green light)
10:11 FAIL (red light)
10:15 OK (green light again despite of failure a few minutes ago)

<!-- gh-comment-id:389429636 --> @mlaitinen commented on GitHub (May 16, 2018): How this would work if the "regular" ping overrides the failed status on the next run? My point: 10:00 OK (green light) 10:05 OK (green light) 10:10 OK (green light) 10:11 FAIL (red light) 10:15 OK (green light again despite of failure a few minutes ago)
Author
Owner

@pladen commented on GitHub (May 16, 2018):

Yes, that seems great.
That's how cronalarm.com is handling it.

The purpose is to give feedback about what's wrong, not to replace logs / alerting system.

Regards

<!-- gh-comment-id:389518969 --> @pladen commented on GitHub (May 16, 2018): Yes, that seems great. That's how cronalarm.com is handling it. The purpose is to give feedback about what's wrong, not to replace logs / alerting system. Regards
Author
Owner

@cuu508 commented on GitHub (May 17, 2018):

I've now added this as an experimental feature: you can append "/fail" to any ping URL and cause the check to immediately go into the "down" state. If its previous state would have been "up", then a notification is sent as well.

I have not yet updated documentation or examples anywhere – I want to trial this feature for a while to make sure there are no corner cases where it does the wrong thing. @pladen and @mlaitinen you are welcome to test it out, both https://healthchecks.io and https://hchk.io are up-to-date.

<!-- gh-comment-id:389956544 --> @cuu508 commented on GitHub (May 17, 2018): I've now added this as an experimental feature: you can append "/fail" to any ping URL and cause the check to immediately go into the "down" state. If its previous state would have been "up", then a notification is sent as well. I have not yet updated documentation or examples anywhere – I want to trial this feature for a while to make sure there are no corner cases where it does the wrong thing. @pladen and @mlaitinen you are welcome to test it out, both https://healthchecks.io and https://hchk.io are up-to-date.
Author
Owner

@pladen commented on GitHub (May 24, 2018):

Thanks, will test that.

<!-- gh-comment-id:391671934 --> @pladen commented on GitHub (May 24, 2018): Thanks, will test that.
Author
Owner

@pladen commented on GitHub (Jun 1, 2018):

i can confirm it works as expected, thanks !

<!-- gh-comment-id:393908667 --> @pladen commented on GitHub (Jun 1, 2018): i can confirm it works as expected, thanks !
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/healthchecks#103
No description provided.