Include workflow-kind tests the ability to check HTTP return codes and POSTs for submitting forms.1 vote
This would be more settings, complexity and cost which is against updown.io’s principle so we won’t do that.
Currently the site only checks the domain home page, it would be interesting an option to scan the site and list all the pages that are inside the site so that we can choose which ones we want to be on the lookout for.1 vote
Sorry but that won’t happen anytime soon. It is much more expensive to test and much less reliable. It’s not off the table for the future but a major leap would have to be made in this domain before I re-consider this.
Check with login credentials. Now we can only see the front page.1 vote
This won’t be done on updown.io because it makes monitoring much more expensive and unreliable as it requires more requests, more parameters, cookie persistence, etc..
Like the test sms message. Send a test alert to the configured email addresses.
Useful for when our email server config changed and we wanna make sure that we still get the alert mails.1 vote
Just add a check to non-existing website for a minute to receive an alert and remove it.
Won’t do yet, this is too restrictive and will be merged into HTTP 2.0.
Customize alerts: you should create custom alerts for (all/specific check(s)) with given (apdex/timeframe):
example.com 0.6 apdex in 15 min → send sms
example.org, example.de 0.3 apdex in 1 hour → send email
This won’t happen, updown.io main goal is to be simple and easy to use, so you don’t have to care about this.
check status code AND content (via regexp) with the same "ping". Currently you should configure 2 "ping", one for the status code and one for the content1 vote
That’s a pretty limited use-case, an API returning the good content but wrong status is pretty unlikely to happen, not worth modifying the product. If you really want to check both, feel free to use two checks with one very slow (10m) so it doesn’t cost much.
It would be cool to add webhooks on event levels.
I just want to call a resource if my server is not reachable, or I just wantro call it if my server started up again.1 vote
It’s simpler this way, you can always filter on the even in your endpoint or use an intermediary like Zapier to do fancy things: https://updown.uservoice.com/knowledgebase/articles/1911991
After more thinking, I’m not gonna do this because having public status page indexed is a feature to me, especially helpful when your website is down and people search “xxxx.com status” for example.
I sometimes see something that makes me think "is this a bug?", but there is no obvious place look it up1 vote
Well we’re not yet swamped by bug reports so just contact us if you see something and we’ll tell you ;)
Right now, Let's Encrypt certificate expiration alert is sent 14 days, 7 days, 1 day before.
I have a certbot that renews it 5 days before.
So every month, I receive alerts 14 days and 7 days for all domains,
which are perfectly normal. Hence, some 'alert noise' that I don't take into account anymore...
Let us select a custom period for SSL expiration dates.
I think globally, with 2 different settings: one for "standard" certificate, the other for 'let's encrypt' certificates.
--> only alert when worth alerting :)
--> smarter monitoring0 votes
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 ☺
- Don't see your idea?