General
89 results found
-
Publish the list of the monitoring nodes via multiple DNS records
When our firewall (PFSense) is given a DNS record (such as monitors.updown.io), it will regularly query this record and turn it into a list of IP addresses - which are allowed to enter our internal network via NAT to query servers.
So if you can setup and update something like monitors.updown.io with the 8 A records to Canada, Los Angeles, Frankfurt... we would have nothing to configure or update on our multiple firewalls 😄
1 voteOk I have created ips.updown.io which will hold all IPv4 and IPv6 for all daemons.
Documentation: https://updown.io/api#dns
-
Add 4 sec / 8 sec to the Apdex threshold dropdown
Some APIs are slower than others but it doesn't mean that they give a bad experience to the client.
An API which has a response time of 5sec by design, currently shows up with red bars on the monitors page which is bad to show on a customer facing monitor page.
12 votesThe 4s and 8s Apdex T have just been added: https://headwayapp.co/updown-release-notes/slower-4s-and-8s-apdex-thresold-260571
Please use them wisely :)
-
Safebrowsing monitor
Ability to monitor if website has been reported.
1 voteThanks for this suggestion. I haven't communicated about this much but I actually already implemented this a couple years ago. It sends alerts and show in the dashboard with a "bug" icon. If you have a website for which this is not working as expected, please let me know so I can have a look!
-
emphasize the 1 month rolling uptime over the 24 hours
It is very easy to accidentally misread this as 100% uptime in the past 24 hours. This makes the page useless as a client-facing custom status page. (with or without whitelabel)
If the "1 month" could be emphasized, or if the 24 hours heading could be pushed down and/or deemphasized it would be easier to read this correctly.
3 votesI just added a small emphasize on the duration.
-
Improve API: allow CRUD on Email Alert Addresses and Pages
We want to monitor 100+ servers, with new clients and servers coming regularly. We already can create the Checks via API - we would love to have APIs to:
- create & update the status page for the client (with multiple checks)
- create & update Email Alert Addresses for clients and bind them to Checks
1 voteThe API to control recipients on checks is already done (see https://headwayapp.co/updown-release-notes/recipients-api-221723)
The one about status page has been added recently, see: https://headwayapp.co/updown-release-notes/status-pages-api-227764
-
I want to implement monitoring from only one country.
I want to implement monitoring from only one country.
I understand why they require more than one due to availability and other issues. However, I would like you to support the case where the web service specification allows access only from one country.1 voteWell as a matter of fact I just implemented a way to bypass this limitation per account, so for people who are aware of the availability issue and risk of false-positive but want to do this anyway I can now allow it.
I’ve just enabled this on your account. If other people are interested you can contact support.
But I still recommend having two locations at least even if it means white-listing some updown.io instances if needed.
-
Alert After X Failures
Please add an option for the ICMP checking that allows alerts to have a threshold that requires a specified number of failures in a row to occur before an alert will be sent. That or allow the ICMP monitor to have a third time period that is the amount of time that the ICMP can be down before an alert is triggered as currently the "Check Interval" is the only time interval and it determines the amount of time in between checks.
3 votesThis is already the case, thanks to the double check we only send alerts after 2 confirmations checks (so 3 down checks in total).
And with the ICMP check in particular, each check sends 4 ping messages (with 5 second timeout) and is only considered down only if all 4 ping failed.
So in total it would require 12 failed ping in a row (from at least two different locations) to send a “DOWN” alert.
-
webhook alias
For reasons we have 3 opsgenie webhooks set up. While I can work out which one is which from the api key its not the greatest experience.
It would be good to be able to set a more human readable alias so that I can easily see which each of the webhooks does when configuring new checks or bulk updating.
2 votesLabels for updown webhooks have just been added:
https://headwayapp.co/updown-release-notes/webhook-improvements-260104
It's not the case for Slack-compatible webhooks though, for them you can continue to use the little hack (which I slightly improved): Add an anchor at the end of the URL to indicate an alias of your choosing. This anchor will not be sent to your server (it's a client-side HTTP feature) but it'll show in your recipient list and bulk edit screen instead of the URL, example:
-
Estonian language translation
I want to help with your amazing projekt and do estonian translation.
2 votesThis was completed in 2021
-
Still cannot prevent an updown.io check from following redirects
I raised this same issue under this discussion almost two years - unfortunately it's been completely ignored: https://updown.uservoice.com/forums/177972-general/suggestions/38068798-add-the-ability-to-disable-following-redirects.
I've worked around this in the past but it's starting to cause problems again, so I'm raising it again and this time I'll expand on the specifics of the problem I'm having.
I run web services from behind Cloudflare. When you set up Cloudflare for proxying, you provide your backend DNS entries to them and enable proxying. They'll then create public facing DNS entries for you that point to Cloudflare, and proxy connections through to your backend. For this, Cloudflare automatically…
3 votesSo this problem has now multiple fixes:
- It's possible to prevent following a redirect by specifying the HTTP status (302, 303, etc.) in the "contains" field.
- When a site has a dual stack redirection server pointing to an IPv4-only server, it'll now automatically disable dual stack monitoring.
- If for some reasons this is still an issue (for example a broken IPv6 you can't remove from DNS), I can still disable dual-stack manually as offered in the comments.
-
Hyperlink to URL from main listing page
I think it would be neat if there was a way to visit the URL from the UI. So if a website is down, I can just click on the URL/Endpoint to go directly to it but currently I would need to click edit and copy/paste it into the URL. Some endpoints are very specific so it makes it easier to navigate to.
I have attached an example suggestion.
6 votesI've just added this link to the dashboard
-
Mark Website as Down when Domain Expires
When a domain has expired and is pointed back to something like a GoDaddy parking page, the monitor shows the site as up. See attached screenshot.
For all intents and purposes, this should really show the website as down. It's easy to overlook for too long when you manage 80 - 100+ sites.
6 votesI am gonna mark this one as resolved as we've now implemented the domain expiration alerts in https://updown.uservoice.com/forums/177972-general/suggestions/36631813-warn-about-expiring-domain-names. It is not exactly the same thing because it will not consider the website as "down" if it still responds with 200OK but at least you can get notified. Also in the example shown in this screenshot, such error would definitely be considered as "down" as it's not even connecting, the monitoring was likely still 200OK because the configured DNS TTL had not expired yet and was still returning the old IP.
-
Expected HTTP status codes
Would be handy to have a simple "Yes a 405 here is okay" or something along those lines, for unusual but expected healthy status. Not sure how much development effort this would be to implement
4 votesThis has just been added, you can now specify the expected HTTP status in the existing “contains” field: https://headwayapp.co/updown-release-notes/specify-expected-http-status-code-211343
-
New "Hidden" status between Private and Public
I'm really needing a "hidden" status for pages, for them to be shareable (to client ..).
Exactly on the same model that Gdrive/Gsuite :
Private > For your eyes Only
Public > Shareable to the world. Can be linked on a public website. Can be found and indexed by google (and you have a lot .. https://www.google.com/search?q=site%3Aupdown.io
Hidden > Only for people who know the URL, to be shared internally. With a long hash key in url that cannot be bruteforced, with meta no index , cannot be indexed by google.
(YES, one could find the url if they hack…
34 votesHello everyone, the Private and Protected visibility for multi-site status page have both been added: https://headwayapp.co/updown-release-notes/private-status-pages-255920
https://headwayapp.co/updown-release-notes/protected-status-pages-259778
Let me know if you have any feedback.
-
notify mail per server
we urgently need the option to enter additional mail recipients per server. The current option is too time-consuming for many monitored servers, since the new mail address is set for all servers when it is created and has to be deactivated again. Alternatively a select/deselect all option per mail address in the bulk edit list.
3 votesHello, this is actually already possible, from the bulk edit page you can select/deselect all by clicking on the rows or columns headers. This allows you to add a recipient, quickly unselect all checks and then select only the checks you want.
-
Make per-stack (IPv4/6) status more accessible
Currently, many of the downtimes I experience affect only IPv6, whereas IPv4 continues to work as usual. However, there are currently several places in updown.io where it doesn’t distinguish between such a partial outage and complete unavailability (IPv4/6 both down). In those cases, it simply marks the check as “down”. This is a real shame given that updown.io already has dual stack monitoring out of the box and is able to show separate statuses on the dashbord like in the attached screenshot (which is awesome!). It would be extremely useful to have this data exposed elsewhere as well, in particular:
- …
14 votesLooks like I forgot to update this but it has been implemented last year: https://headwayapp.co/updown-release-notes/less-visibility-for-partial-connectivity-issues-(ipv6-only)-176227
Since then partial (IPv6-only) downtimes are easier to distinguish and they don’t impact global availability numbers.
-
Zapier variabelen
Ik wil graag de Updown.io meldingen door Zapier laten afhandelen. Echter het opmaken van de berichten naar derde apps kent weinig variabelen. Is het mogelijk om de huidige "Description sentence" op te knippen in lossen variabelen zodat we in staat gesteld worden om zelf berichten op te stellen?
Bijvoorbeeld:
1. Gebruikersvriendelijke naam
2. De monitoring URL
3. Event type up/down/ssl invalide
4. Down since
5. Reason
6. Etc.3 votesHi,
First of all please write in English here so other users can benefit from this too.
About Zapier variable, it is totally possible to write more custom messages with many variables but in that case you need to use the individual specific events (see screenshot) instead of the generic one (“new alert”). We can’t provide all variables in the generic event. You need to use Zapier integration v1.1.2 at least to see all events here as I recently made more of them visible.
-
Meta tag "noindex" on public status page
It seems that Google has indexed my public status page, in all available languages. This isn't really necessary; it would be useful if there was some way for me to turn on a "noindex" meta tag, preventing search engines from indexing it.
12 votesThe new Protected status page visiblity give a more secure access with "noindex" by default and a non-guessable access_key:
https://headwayapp.co/updown-release-notes/protected-status-pages-259778
The Private status page visiblity can also help of course if no foreign access is required (for logged in user only).
-
Make a warning icon appear when an SSL is within the 30 days expiry
Make a warning icon appear on the. main checks page when an SSL is within the 30 days expiry. Ive just added a site now to test your system and it expires in 6 days time, so its missed the 30. 14 and 7 and its not drawing my attention to the fact it needs renewing very quickly.
3 votesThis has been implemented last year: https://headwayapp.co/updown-release-notes/improved-ssl-expiration-warning-149107
Expiring soon certificates are now showing in the dashboard listing and in the weekly report so it’s harder to miss them. -
Having a global domain as CNAME for all status pages instead of one per status page
I would like to be able to have "https://status.domain.com/xxxx" instead of "https://xxxx.status.domain.com" :).
This could allow me to avoid touching my DNS all the time for every check.
6 votesAlthough this is not an official feature, this is now possible thanks to the multi-site status page.
If you create a public multi-site status page with a custom domain (example: demo.updown.io), you can then access individual status page from the same custom domain (example: https://demo.updown.io/ngg8), and this is true even for sites which are NOT listed on this status page (as long as the individual status page is public of course).
- Don't see your idea?