[GH-ISSUE #367] Badge with uptime % #280

New issue

Closed

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

kerem commented

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

Owner

Originally created by @BobCashStory on GitHub (May 1, 2020).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/367

it could be great to have badge option with uptime Ratio like that :
Screenshot 2020-05-01 at 15 30 14
It can be nice to have it in the check page too .

Originally created by @BobCashStory on GitHub (May 1, 2020). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/367 it could be great to have badge option with uptime Ratio like that : <img width="163" alt="Screenshot 2020-05-01 at 15 30 14" src="https://user-images.githubusercontent.com/47117399/80808838-acf5e800-8bc0-11ea-8cda-0a3310df2fd8.png"> It can be nice to have it in the check page too .

kerem

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

closed this issue
added the
feature
label

kerem commented

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

Author

Owner

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

Thanks, this is an interesting idea, but I'm not planning to work on this.
Badges are public, can be embedded in public documents, and so need to be generated very efficiently – we may need to serve hundreds of badge requests per second. With the current data model the downtime calculation is relatively expensive. Changing the data model would be a major task, and, for me, the cost-benefit ratio isn't there.

@cuu508 commented on GitHub (Nov 19, 2025): Thanks, this is an interesting idea, but I'm not planning to work on this. Badges are public, can be embedded in public documents, and so need to be generated very efficiently – we may need to serve hundreds of badge requests per second. With the current data model the downtime calculation is relatively expensive. Changing the data model would be a major task, and, for me, the cost-benefit ratio isn't there.