mirror of
https://github.com/healthchecks/healthchecks.git
synced 2026-04-25 15:05:49 +03:00
[GH-ISSUE #874] Feature request: SLA availability computation #613
Labels
No labels
bug
bug
bug
feature
good-first-issue
new integration
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/healthchecks#613
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rudolf-bauer on GitHub (Aug 8, 2023).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/874
According to my SLA with a customer, I need to compute the monthly availability (uptime) of my services. Some of them are monitored by healthchecks on a per-minute basis. Threfore, I used the management API to get all flips of the corresponding checks and compute the downtime in a specified time range. Does it make sense to add such a page (html/pdf) to healthchecks? E.g. in the check's details?
Off-topic: I love healthchecks, great product!
@cuu508 commented on GitHub (Aug 10, 2023):
In the check details pages we already display the number of downtimes and the total duration of downtimes for past 3 months:
Using the data already there, it would be easy to also calculate uptime as percentage. In the above example, where it says "21 hours total", we could calculate the uptime percentage as 21 / (31 * 24) = 2.8%, and show it as: "2 downtimes, 21 hours total (97.2% uptime)".
Would something like this work?
When calculating SLA, do you calculate it for every month separately, or do you calculate it for a sliding window of last 30 days?
@cuu508 commented on GitHub (Aug 28, 2023):
No reply, closing.