General
109 results found
-
Integration with status.io
Provide integration with status.io, so your status page is updated automatically when updown detects an issue.
As a data point, status.io is another well known "status page" provider. They're actively developed (unlike Atlassian StatusPage these days), and used by a lot of places.
1 vote -
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 votesGood suggestion, that is definitely a pain point. But I have a little hack for this (which I personally use), not very pretty but efficient: 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 so it makes it easier to distinguish URLs, example:
https://example.com/xxxxxxx#project-A
https://example.com/yyyyyyy#project-B -
Estonian language translation
I want to help with your amazing projekt and do estonian translation.
2 votesThanks for your offer, I just sent you the translations by email.
-
Custom scheduled check interval
Add please a possibility to create a custom time for trigger a check.
Example: 10am every Friday5 votes -
Microsoft Teams integration (not via 3rd party)
Sending messages through a third party is not that great and imho should not be necessary for a large service like MS Teams.
76 votes -
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 visibility for multi-site status page has just been added: https://headwayapp.co/updown-release-notes/private-status-pages-255920
The Protected visibility will also be added soon!
I'm keeping this suggestion as "started" and will mark it as "completed" only once it's the case.
-
prometheus integration
I saw that a Grafana plugin was suggested and I am all for it, but even better might be a Prometheus integration. Prometheus pulls the data in and stores it. Once it's in Prometheus it can be displayed in Grafana pretty easily. I suspect that since there is already an API for updown it's just a matter of making the two systems data connect but that's a bit out of my grasp to do it myself.
12 votesHere is a third-party Prometheus Exporter for updown.io graciously provided by @DazWilkin: https://github.com/DazWilkin/updown-exporter
-
Display days to expire in listing
Adding a column that shows the days to cert expiration would be so handy. Also, if/when you succeed with the domain expire project, another column showings days til domain expiration again would be useful for me. Possibly these are optional columns for those that want in their display grid?
6 votes -
JSON version of the status page
Having a JSON version of the status page allows any possible integration with 3rd party tools/dashboards. Lowers the amount of API requests required to get similar content (even though I think not all of the information that is currently visible on the status page is also available using the existing API). Probably you want to put it behind the API key except maybe for public status pages.
13 votes -
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 votesHi, 2 months ago we started providing canonical URLs so search engines would only display a single result (without the localized version) but it looks like this is not enough and multiple versions are still indexed. We’ll probably add some noindex to help with that.
On the other end we’re not gonna totally block the indexing of the main status page because this is a feature, being able to lookup a status page when the monitored service is down can be useful. -
Grafana plugin
This has been suggested by a client so I created the suggestion to gather interest:
It would be great to see an updown plugin in Grafana, From what I know from grafana you would need to create some API endpoints for data output and then use it as data source and configure some demo dashboard's, here is example I found https://grafana.com/grafana/plugins/raintank-worldping-app
3 votes -
DNS record checks
Hi,
I have implemented a simple php script on one of my servers to take a query via GET method and returns the requested DNS record.
The site is restricted to updown.io servers and uses a URL in the following format :https://webserver.com/lookup.php?T=A&D=google.co.uk&R=IP
This uses the following fields :
T - Type of record to return eg. MX/A/TXT
D - Domain to check eg. google.co.uk
R - Record field to return. eg. ip for ip address
The server code simple checks if the record type is a valid one we accept, checks the domain name is in a valid format…4 votesThanks for the suggestion, I’ve just merged this with another one about DNS check. This is something we’re thinking about but is not planned yet.
In the meantime what you made is a great workaround, if other users are interested I encourage them to leave a comment here with a way to contact them so you may give them the URL of your service if you want.
-
Show Total Time on dashboard
I like to see the Total Time from the last 24 hours (so REDIRECTIONS + NAME LOOKUP + CONNECTION + TLS HANDSHAKE + RESPONSE TIME) on the dashboard.
Would be very nice to not only see the Apdex, but also the Total Time for all websites at one overview page.
7 votes -
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 votes -
Provide an explanation of what "Redirections" is.
Trying out the service and first thing I noticed is "Redirections" is about 50% of the time used. It would be great if you could provide a document or link as to how you are calculating this and what we could do to reduce it.
4 votes -
Allow Green Status when using letsencrypt staging CA
In dev environments is common to use the letsencrypt staging CA rather than the production one .
This CA does not verify using the standard system ca store.
Would be useful to allow marking the letsencrypt staging ca as allowed on a per check basis
1 vote -
Break down the time taken by redirects since they're often a key part of the user experience
Currently updown.io breaks out the time of normal requests into:
- name lookup;
- connection;
- tls handshake; and
- response time
but shows redirects as a single block of time. It would be useful to see redirects broken out the same way.
Users often type naked domains, like example.com, into browsers. That might lead to this sequence of redirects:
http://example.com/ -> https://example.com https://example.com/ -> https://www.example.com(HSTS preload requires the first redirect; you can't go straight from http://example.com/ to https://www.example.com.)
Depending on how you're handling both http and naked domains the time for the redirects can be much greater than the time of…
11 votes -
Finetune the SSL expiration alert period
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...Suggestion:
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 monitoring5 votesHello,
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.
-
Test based on hash
It would be handy if instead of content we could choose to hash the response and test if the response matches the hash.
1 vote -
South America checkpoint
Hello, I suggest that a South American checkpoint is a priority. I have (among others) websites in Spanish and Portuguese, and although Spain and Portugal are in Europe, the majority of users in these languages turn out to be from South America. If you need a VPS in Brazil, I can recommend Virtuaserver (I had a good experience with them), or there are many others. Best wishes and keep going.
34 votes
- Don't see your idea?