Jimmy Shimizu
My feedback
2 results found
-
1 vote
An error occurred while saving the comment -
148 votes
Hello everyone, I’ve just added a way to get the detailed results from the last 5 checks before downtime and recovery to the downtime API, all you have to do is add the “results=true” parameter, like this:
https://updown.io/api/checks/yyyy/downtimes?api-key=xxxxxxxxxxxxxx&results=true
Warnings:
- This API is alpha version, it can still change.
- The response can be huge, I recommend using this only when needed and with http gzip compression if you can.
- The dual stack results (IPv4 and IPv6) will NOT repeat “body” and “received_headers” if they are the same as in the parent result record, to save space.Let me know what you think!
Jimmy Shimizu supported this idea ·An error occurred while saving the comment Jimmy Shimizu commentedThis is a really helpful feature for reporting back to stake-holders. I tested the API, and although you get time and duration of a failed check, I would also like to see (both on the web page and the API) from which location/locations the check failed. That is a nice way to identify if there is a routing problem causing a false positive, or if it is a wide-spread outage.
I would even be satisified if failed locations was just part of the slack integration, giving me direct info to evaluate if it is a partial outage which is region-specific.
You can specify different notification settings per channel in slack, meaning you can tell people to set it to "Every new message" instead of "Just @mentions".
It's not perfect, but a big improvement. Downside is that if people start chatting about incidents in that channel, it becomes annoying.