AdminAdrien Rey-Jarthon
(Founder, updown.io)
My feedback
30 results found
-
14 votes
We don't want to invest any time or money in this for now. We already provide fast and robust push-notification friendly channels (e.g. Telegram, Slack, SMS) and the website is responsive.
One of our clients did start working on a third party app though, so you may give it a try using this TestFlight link.
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment Well it's in some places already but maybe not where it's most needed or tought of:
1. If you hover the downtime section (red line) in the uptime chart, you can see the time of start, reason for downtime and time of end (if finished).
2. In the alert up/down notifications of course, and when you receive a "still down" alert for example, it tells you for how long it has been downAre there other places where this timestamp should be displayed in your opinion?
-
8 votes
An error occurred while saving the comment @Seth it looks like you're talking more about this kind of tags: https://updown.uservoice.com/forums/177972/suggestions/9571917 ?
This suggestion is about giving SMS or email addresses a name. -
348 votes
This is not something I have plans for in the near future because of the complexity and the wide other range of feature requests it would attract due to bigger clients (permissions, roles, audit logs, SSO, SLA, etc...). But I might do it at some point if I want to target bigger clients.
An error occurred while saving the comment Totally understandable, thanks for your feedback.
This is not something I have plans for in the near future because of the complexity and the wide other range of feature requests it would attract due to bigger clients (permissions, roles, audit logs, SSO, SLA, etc...). But I might do it at some point if I want to target bigger clients.An error occurred while saving the comment @Frank if you publish your status page you can then share the link for read-only access to unauthenticated people.
-
65 votes
Hi all, there's now two options for that which are:
1. Through Zapier (we just added native Zapier integration): https://updown.uservoice.com/knowledgebase/articles/1911991 Using this you can connect pushover.net and receive alerts from updown.io. I'm keeping this suggestion "under review" to gather interest about a native integration with pushover.
2. Using a DigitalOcean function to catch the webhook and push it to pushover (contributed by Marc): https://github.com/MarcHagen/function-updownio-to-pushover
An error occurred while saving the comment Hi Michael
It likely will because I see it gaining popularity, but considering the alternatives way to connect it already: Zapier, the function by Marc, or even their Email gateway (https://support.pushover.net/i29-e-mailing-notifications-to-your-devices), this is not in the short-term roadmap.
You may want to try their Email gateway to avoid intermediaries, I'm not sure how the formatting will come out though.
An error occurred while saving the comment Thanks Mark! I just added your function to the list of options.
-
6 votesAdminAdrien Rey-Jarthon
(Founder, updown.io)
supported this idea
·
-
4 votes
One important thing to note here is that having an invalid certificate does NOT prevent the expiration notifications. This is independent so you can keep an "invalid" certificate forever (updown will not notify you again about this) and still benefit from expiration warnings. This way we already kind of "tolerate" this use-case of running a non-publicly trusted certificate.
About the suggested changes, I would like to avoid the custom cert/CA UI because that's a lot of added complexity for a very small use-case among my clients. It'll generate more support also as people will wonder what this do, try to upload other certificates, it'll be annoying for self-signed certificates, etc... The UI to manually "acknowledge" that one cert should be considered valid though sounds more doable for me, I'll keep this suggestion to track the demand and will probably add this someday.
An error occurred while saving the comment Thanks @Javier, I made a longer reply by email but the TL;DR for people following this suggestion is that these websites not only use a custom CA cert, they also require TLS Client Certificates. So even implementing custom CA root cert would not be enough, and implementing also client certificates makes the endaevor quite bigger. The clients who needs this are very few and mostly enterprise which updown does not target. So I'm not gonna move ahead on this one, but I'm keeping the suggestion open to gather interest for later, and so I can notify you in case of changes.
The "acknowledge" mentionned earlier might be implemented but it wouldn't help well in @Javier case and there's dozens of way to implement this so I'm still waiting for more occurences and experience before doing it.
An error occurred while saving the comment Thanks for your feedback @Javier. Do you have some example websites and the associated CA public key so I can run some tests? You can send this to support@updown.io. Thanks.
-
6 votes
An error occurred while saving the comment @Gautier unless I misunderstood something no they don't, even if you configure a custom domain, the check "Alias" or URL is displayed inside the page. The Alias already allows you to hide the URL and display something else instead, but what this suggestion is requesting is to have a different name shown for the public (e.g. like a "public alias") than the one shown privately in the dashboard.
-
3 votes
An error occurred while saving the comment I suppose you meant "SSL" instead of "SSH"? (I updated the title). The SSL expiration alerts are already sent to the same email selected for check alerts (they do not support slack, telegram and others channels though..) so they are already following this configuration.
The Domain expiration is not at the moment though (So if this is what you meant I agree it should probably follow the same alert emails).
Could you please confirm if this is what you meant? your use-case? Thanks. -
5 votes
Hello,
Actually 14, 7, 1 is already the special schedule for let’s encrypt certificates. This is automatically detected by updown.io so you don’t have to, normal 1-year certificates get an additional 30 days reminder.
The threshold for let’s encrypt certs starts at 14 days because the default renew delay is 30 days before expiration: https://certbot.eff.org/docs/using.html. This can be down to 23 days with a weekly cron for example (pretty common) so that’s why we chose 14 days, so you have plenty of time to renew but still have time to investigate and fix any potential auto-renew issues.
If you’d rather renew your cert only 5 days before expiration that’s up to you but we won’t recommend or support this configuration as we consider it dangerous ☺
I’ll mark this suggestion as “Under Review” to measure the need for this.
An error occurred while saving the comment @Cilex when is OVH renewing?
-
7 votes
An error occurred while saving the comment @Stefan thanks for commenting, the suggestion you are talking about (sometimes also called "pulse" or "cron" monitoring) is actually planned and tracked here: https://updown.uservoice.com/forums/177972-general/suggestions/5586072-periodic-task-cron-monitoring.
The suggestion from Michael here is more about some kind of proxy daemon you could install so updown can access your private network "directly" (which is less likely to happen).
-
2 votes
An error occurred while saving the comment +1 for iDeal
AdminAdrien Rey-Jarthon
(Founder, updown.io)
supported this idea
·
AdminAdrien Rey-Jarthon
(Founder, updown.io)
shared this idea
·
-
106 votes
Before this is implemented we can recommend some alternative services:
- https://healthchecks.io (SaaS or open source: https://github.com/healthchecks/healthchecks)
- https://deadmanssnitch.com
- https://cronitor.ioAn error occurred while saving the comment Sorry but I can't give any ETA as this will depend on the time I have and other higher priority task that comes before. If you are hesitating on switching because of this I recommend staying with your current provider until you receive an update on the status of this suggestion. Or be prepared to keep both tools for a while.
An error occurred while saving the comment Hello and thanks for your suggestion.
The first option you're talking about where you would "refresh" the up status on your end is actually planned for later here: https://updown.uservoice.com/forums/177972-general/suggestions/5586072-periodic-task-cron-monitoring (under the name "pulse monitoring", "cron monitoring" and various other versions). I am actually gonna merge these suggestions together so you get the updates from the other suggestion and it adds up your vote too.
Also as you said one alternative which is currently possible is to expose a small HTTP/TCP service to the outside for monitoring purpose only and configure this one in updown, some of our clients are doing this to "expose" the status of internal services. But I totally understand if you don't want to do this of course.
In this case what I would recommend would be to use one of the existing pulse monitoring services discussed in https://updown.uservoice.com/forums/177972-general/suggestions/5586072-periodic-task-cron-monitoring before updown implements this, and once we do and if you want to consolidate everything in updown.io it should be easy to switch over.
An error occurred while saving the comment Thanks for bringing this one to my attention, looks nice. I'm adding it to the list of alternatives in the description too so other people can use it.
AdminAdrien Rey-Jarthon
(Founder, updown.io)
supported this idea
·
AdminAdrien Rey-Jarthon
(Founder, updown.io)
shared this idea
·
-
1 voteAdminAdrien Rey-Jarthon
(Founder, updown.io)
shared this idea
·
-
3 votesAdminAdrien Rey-Jarthon
(Founder, updown.io)
shared this idea
·
-
11 votes
An error occurred while saving the comment @Tony you can use https://tools.pingdom.com/ for example to get a waterfall view of the different redirection requests detailing how much time they took and from which URL you passed by.
It's also possible with local tools like curl if you're familial with command-line (https://dev.to/yuyatakeyama/how-i-measure-response-times-of-web-apis-using-curl-6nh).
An error occurred while saving the comment Unfortunately the library we use to issue requests (libcurl) doesn't provide more detailed timings on the redirection intermediary requests, also presenting this amount of information would be much less readable so I don't think we'll do this but I'll keep the suggestion open to measure interest.
Alternatively you can of course mesure the performance of your different redirections on your side and if you want to more detailed metrics from our locations you can contact us by email and I'll give them to you.
-
147 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!
An error occurred while saving the comment That's a good point Jimmy, I'll try to add more details to the downtimes API.
AdminAdrien Rey-Jarthon
(Founder, updown.io)
supported this idea
·
An error occurred while saving the comment 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.
An error occurred while saving the comment @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 ☺
-
7 votes
An error occurred while saving the comment Hello,
Thank you for your suggestion but I'm not sure how would this make the service better to everyone? -
34 votes
An error occurred while saving the comment Thanks for the recommendations, we'll keep that in mind.
-
4 votes
An error occurred while saving the comment In the meantime you can ask me to bulk update for you if it's not too often ;)
Hello Kurt, thanks for your interest. The developement of the iOS app can be followed here: https://vincentritter.com/projects/status-for-updown-io
Vincent also shared with us the TestFlight link for people who want to give it a try: https://testflight.apple.com/join/F1KmUg6K
It's a ReactNative app so it'll be able to run on Android too (and Vincent plans to do it) but it's not the case at the moment.