Feature Requests Log of uptime/downtime
Completed
Maybe I overlooked it, but is there a log of the incidents available? Simply a text list of the times when a website went down, and when it was up again.
Harry Oosterveen
Created on November 06, 2016 · Last update on October 02, 2024
16 Comments
I'm particularly eager to find a way to get a list of recent pings, the same as in the email. It would be ideal if I could click from the dashboard/index page of all my checks into individual request histories. The link I'm looking for is: http://updown.io/downtimes/590a04fc18b2ad5dcc225f5a/results/590a063ecbce6b27d2ad7fb0
Maybe you can also add a function to comment the downtime. So we can log the issues to our customers for example like "planned maintenance" or "server restart" or so.
Thanks!
@Lars yes, that's in another idea you can vote for: https://updown.uservoice.com/forums/177972-general/suggestions/15589635-allow-text-updates-for-incidents ☺
I'd like to go back to my ISP and say "here are all the failures you've had in the last 3 months/1 year", with data to back it up. This would be amazing.
THanks!
Good idea, if you want data you can already use the downtime API (https://updown.io/api#rest) no special skills needed, just put the url in your browser with your API key and the check token (visible on the status page URL) to get all the downtimes with precise time. You can use a json formatting extension or website to make it more readable if needed.
This 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.
That's a good point Jimmy, I'll try to add more details to the downtimes API.
+1 from me, as a starter it'd be nice to have the API return more details.
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!
Looking good :) just tested it on one of my checks and it shows what I'd like. I especially like the details_url
The data being returned in the API is super-helpful, especially the received headers! I would love to see these on the status page in some form.
Lovely! Would love to see this through the UI as well.
Would love this in the UI as well
First version of the downtime list (and detail) has just been deployed ! See the annoucement here: https://headwayapp.co/updown-release-notes/downtime-list-301793
Let me know what you think :)
In particular I have one question: I'm thinking about linking the downtime detail page (with the timeline) in alerts notifications (would be quite helpful). But as this page currently requires authentication it's gonna be impossible to access for some people.
The result page (showing only one request) is already public and it was linked in the email alerts.
The link is not guesssable so the problem is not really public access, but more if you want e.g. external clients receiving alerts (but without access to the updown account) to be able to see full details or no.
Shall I make the downtime details page accessible from all alerts ? and if yes to everyone or only people with updown login ?
Excellent work. There are, as usual, some very nice touches; it was thoughtfully designed.
Really nice! Great! Also the history and retry command is really cool!
Sign in to comment