Granular Uptime Mertics
- Under review
- Subscribe
|
M |
Mark Kistler |
Update the uptime calculation only to include some of the statuses. For example, we move an incident to monitor when service is restored, but we want to keep a close eye on it. We don't want that time in monitoring to count against the downtime. Also, we use different statuses to tell the whole story of the incident. For example, the system may be slow but still operational, or only parts of the system are unavailable, but most of it is available. When we report on uptime, we want to be able to show precisely what has been going on. This also helps with learning from incidents, are most of our incidents are performance-based or outage based.
Activity Newest / Oldest
Joshua Williamson
I upvote this...essentially uptime calculations should relate to durations of specific component statuses, not to an event (Incident) based on the presence or absence of a flag (count towards down time?). We should be able to configure which statuses count towards downtime by default, then have the ability to override that for a specific Incident - I believe this functionality was proposed by Evan before he left
Customer Success
Status changed to: Under review