General
60 results found
-
Negative text
I'd like to fail a monitor when specific text is found (opposite of the existing text matching). Use case is my human-readable status page that will say "Database: BAD". I'd like to trigger an alert when the text "BAD" is in the response.
Thanks for the simple and useful service.
1 voteThanks for this suggestion but I decided against implementing this feature. Because I think it's way too easy to generate false positives where your service is down and you're not notified because it's not the case you expected and entered in the search. For example your page could later change "BAD" to "bad" or "DOWN" or whaterver, or your page could simply stop working and returning any text or return an error message instead, and you don't want those to be considered UP. And even if it's not technically my fault, friends don't let friends build brittle monitoring ☺
The better option if you already have a custom status page is to either return a custom HTTP status depending on global state, applying the rules you want (e.g. any service is bad, status = 500) Or you can include a global text status saying something like "Global: UP" and do…
-
Toogle ipv6 connectivity check
Currently, I have a setup, where I can't influence, if my DNS has a AAAA entry for my domain. Therefore, updown.io check, if my service is accessible via ipv6. However, I can't serve my services via ipv6.
This is fine for me, as the browser can work with that and chooses ipv4, if it can't connect via ipv6. Therefore I would like to disable the updown.io ipv6 check for certain services.
3 votesHi, if you're really sure you want to keep this incorrect configuration and understand the consequences, I can disable the dual-stack check monitoring for you, let me know which account/check this is about on support@updown.io.
I'm not gonna add a setting for this because then it would be too easy to keep such invalid configuration online.
-
Webhook for updown.io Status Page
Currently, the only way to subscribe to the updown.io service Status page is via email. Please allow webhooks to retrieve these alerts. It's extremely important we're notified of any issues (or maintenance) currently being experienced by updown.io if we're to trust it to monitor our services.
It says "Choose from the options below to automatically receive notifications when we update the status site", but there's only one option, which is email?
3 votesThanks for this suggestion, this is unlikely to happen though, this status page is made with https://staytus.co/ which does not offer this option and it would be way too unreliable for people using it anyway (almost never any webhook, hard to make sure the integration is still working, endpoints will go down among the years and people will never remove them, etc..) The email notification is the preferred way of notification.
-
Custom/more monitoring locations
Hello,
Are you planning to add additional monitoring locations?
Or maybe even the possibility to add a custom one?1 voteNot really, if you’re looking for some specific location please vote for it on the specific suggestion in https://updown.uservoice.com/forums/177972-general?category_id=389281 or add your own, with some justification about why we should add the location you want.
And about custom location if you’re talking about a self-hosted monitoring daemon there is not plans about that.
-
DMARC Monitor
It would be awesome if updown.io could check DMARC reports.
3 votesThanks for the suggestion! this is not really something related though (uptime monitoring) so it would be a whole different product. For that I clearly recommend https://dmarc.postmarkapp.com (which I use)
-
Longer timeout than 2 seconds.
We are sysadmin that use services like this + webhook to wake up sysadmins in the middle of the night if something goes down.
2 second max response is too short. Sometimes a server can become overloaded and be sluggish for a moment, and thats OK, and should not be considered a downtime.
If sysadmins are woken at 3am for a brief period of sluggishness, then they cant perform well the next day fully sleep deprived.
Need longer options. 3,4,5,..10 second ranges
4 votesThis is not the timeout, this 2 sec max select box is about Apdex threshold and performance metrics.
At the time of writing the timeouts are:
- for HTTP and TCP checks: 10sec connection + 30sec response
- for ICMP checks: 4 pings with 5 sec timeout each (if any ping success the check is UP) -
Regex check of response body
We have a single health-check endpoint which returns health of various modules of the system in JSON format. I would like to define these different components as separate monitoring targets in updown.io. Regex checking of the response would fit the bill.
3 votes -
Support SAML single-sign on (SSO); e.g. ADFS
I have a SharePoint site I need to monitor, but it does not allow anonymous login. I need a way to authenticate with it.
1 voteThank you for the suggestion but we’ll not implement something this specific. This is not compatible with updown.io’s goal to be simple and inexpensive.
-
SLOs and SLA for updown.io itself
More SLO's and SLA's for uptown.io itself. In exchange for more $.
1 voteUnfortunately I’ll probably never implement any SLO/SLA as it’s not sustainable at my size (solo founder), it wouldn’t really make sense to refund money on a service costing so little IMO and most importantly I’d rather put efforts into making the product better than spending my time negotiating deals with bigger companies. I also prefer the simplicity and fairness of everyone paying the same price (proportional to usage) and having the same (good) service.
-
Customise (on/off) Default Notification Channels
I would like to set which Slack Alert Channels (but this idea applies to all notification methods) should be default on or default off.
I have a couple of channels I need just for specific high priority notifications. I don't want them accidentally switched on for every updown.io entry that is added
11 votesI don’t really want to add too much complexity here but for the record when creating a new check not all recipients are active by default. updown takes the last created check as an example and copy these values.
This means it’s a little smarter and if you have some recipient always on and some almost always off, you’re likely to get this right by default and might only have to correct one or two which makes it more acceptable.
-
Allow cachebusting URLs
I use updown to check a url that is behind a caching CDN. If the origin server goes offline, real users making requests for new URLs will see errors, but I will not be notified of downtime: the updown check will still succeed since the URL it is checking has been cached.
I'd like the ability to add a random string to a URL each time it is checked, so that requests bust through the cache and check that both the CDN and origin server are online
4 votesIndeed that’s a classic problem but it’s better solved using the standard Cache-Control header to disable caching, and this one can already be set on updown.io using the customize request form (</> icon).
-
Screenshots
Add screenshots to the reports, so we don't have to setup that with another provider seperatly
5 votesIf you’re talking about screenshot of the page or website, that is not possible because updown does not render the website (by fetching CSS, images, javascript, etc..). We only request the HTTP endpoint and eventually download the body if you specified a string to search on the page (in which case you can see the raw HTTP body in the alerts)
-
I would like to do checks of backlinks with updown. Its more than enough to check them once a day not every hour.
Increase the frequency choice to 1 day
1 voteGenerally speaking this will not be added because it is not worth it with our pricing. But if you have a lot of sites, we can discuss custom periods for your accounts (e.g. 2h, 3h, 6h) to lower the cost. You can contact us in this case.
-
Add 15 minutes and/or 20 minutes check intervals
I understand the drive to keep the number of options small, but to me there is pretty clearly a "hole" in the available check interval options.
For reference, current interval options are:
15s, 30s, 1m, 2m, 5m, 10m, 30m, 1hMy "standard" checks for important stuff use a 5 minutes interval.
I'm looking to lower my costs by using a larger interval for some of my less important stuff, but right now my only options are the 10 minutes interval, which is not really going to save me enough money to be worthwhile, and the 30 minutes interval, which would…
4 votesIndeed we don’t want too many options for simplicity but we do support custom intervals per client if needed so I’ve just granted you access to 15m and 20m intervals on your account.
-
1 ping par jour
Ping une seule fois par jour, a une heure precise
1 voteThanks for the suggestions but this would change the UI a lot and doesn’t fit our pricing model so it’s not going to happen.
-
More heck periods: 2h and 4h
More check intervals: 2h, 4h.
2 votesIntervals above 1h may be available on demand depending on how many sites you are monitoring. Please ask support if you want.
-
Higher timeout threshold
We have a couple of long running dashboard pages and a higher timeout threshold would be useful
3 votesThe current values are 10s for connection timeout and 30 seconds for response timeout. I do not plan on allowing to increase those as it’s already pretty high.
-
Add a "Does not contain" option
The content on the site may vary a lot, but it should never include words like "exception" or "error", which is what we want to check for.
9 votesSorry but this won’t be added, we consider it to be a bad practice as this would miss most actual errors returned by your servers and drastically reduce monitoring quality (which would then be blamed on us). If you don’t care about the content present, just don’t use this feature and rely on standard HTTP status check.
-
Headline annual rolling uptime
The last month rolling uptime percentage (large headline) is really helpful as it shows the most recent performance. Beside it, I would like to see the Annual Rolling Uptime. If the account has not been active for a year, it should show the period since the account was opened. This is important because after six months, the month-by-month view will have been deleted.
That said, this is the best online service that I've discovered this year.2 votesThanks for your feedback, unfortunately we can’t really add all the number people want, the status page already have lots of them. We’ll probably add the ability to go back in history in the future (on the calendar view for example) but we most probably won’t add an annual uptime in the headline. You can get this number from the API if you want it though, the history is kept forever at the data level.
-
Alert after N periods
In order to avoid false alarms, it would be great to have a per-check variable to define how many failed pings to wait before alerting.
3 votesWe already do 2 double checks before notifying, which is enough to eliminate any false positive. If you want to ignore real but small downtimes, you should increase the check period.
- Don't see your idea?