[GH-ISSUE #244] https://fq.dn/ping/token/fail="Message" #177

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

Originally created by @lazardanlucian on GitHub (Apr 24, 2019).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/244

Hello, I think this could be usefull in this scenario:
Instead of creating 3 healthchecks for three different services/servers
You could use the same token across multiple servers/scripts
And add a failure message that you could send, just like $NAME, $STATUS, a $MESSAGE could be sent.

This could be limited/truncated to 20 chars, it doesn't have to be very long, so the database won't get clogged. and maybe strip non a-Z + 0-9 + dash characters for the safety of other integrations where messages end up.

Another use case is: RAM/DISK, where you could pass the percentage.
Or combined, consider a cluster of three machines, that are identical in set-up and serve the same product, you could just copy the same cron/checks including tokens, and pass the machine id/number on a failure.

eg.:
https://fd.dn/ping/token/fail=Sv1-sda2-20pct-free
or
https://fq.dn/ping/token/fail=Sv2-200M-RAM

Originally created by @lazardanlucian on GitHub (Apr 24, 2019). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/244 Hello, I think this could be usefull in this scenario: Instead of creating 3 healthchecks for three different services/servers You could use the same token across multiple servers/scripts And add a failure message that you could send, just like $NAME, $STATUS, a $MESSAGE could be sent. This could be limited/truncated to 20 chars, it doesn't have to be very long, so the database won't get clogged. and maybe strip non a-Z + 0-9 + dash characters for the safety of other integrations where messages end up. Another use case is: RAM/DISK, where you could pass the percentage. Or combined, consider a cluster of three machines, that are identical in set-up and serve the same product, you could just copy the same cron/checks including tokens, and pass the machine id/number on a failure. eg.: https://fd.dn/ping/token/fail=Sv1-sda2-20pct-free or https://fq.dn/ping/token/fail=Sv2-200M-RAM
kerem closed this issue 2026-02-25 23:41:28 +03:00
Author
Owner

@lazardanlucian commented on GitHub (Apr 24, 2019):

Actually, i'm inserting warning or critical tags on the service from the check, seems enough in a way...

<!-- gh-comment-id:486224681 --> @lazardanlucian commented on GitHub (Apr 24, 2019): Actually, i'm inserting warning or critical tags on the service from the check, seems enough in a way...
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#177
No description provided.