General
92 results found
-
Custom Logo
I think a custom logo has been suggested before in a comment (https://updown.uservoice.com/forums/177972-general/suggestions/33892252-custom-css-for-public-status-pagess), just wanted to raise it a suggestion now
25 votes -
STARTTLS check for SMTP servers
Ath the moment SMTP ports may be checked for responsiveness but not for valid connections. Interesting would be:
- check if there is really a SMTP server
- check for STARTTLS
- check for valid certificate / expiring certificate
- check for MTA-STS/DANE
15 votes -
Add notification escalation
Add notification escalation.
Add a method for responsible people to aknowledge reception of an alert. Add an escalation of alerts in case someone did not respond in due time (15 min, or parametrable).
1 vote -
Support WebSocket endpoint
Allows to monitor WebSocket only endpoint (ws:// and wss://)
25 votes -
Alias for alert email addresses
When using a service such as StatusPage for client updates, it provides a long unique email address for each type of alert we need to monitor. Without an alias it’s difficult to see if we are selecting the correct alert when assigning to each monitoring process.
6 votes -
More Bulk Options
It would be useful to have bulk editing options for the "check interval" and "monitoring locations".
4 votes -
@channel support for Slack integration
When a Slack notification for downtime comes through, I'd be happy to have it use @channel, to increase the chance that anyone on that channel will know about downtime as soon as possible. I don't see any way to configure that currently.
1 vote -
Add clarification on APDEX hourly chart
I don't know why, but I always get confused if the far right is the current hour or the far left is the current hour. A mouse-over, tool tip or guide that just says "current hour" or "24 hours ago" would help clarify at a glance.
2 votesIndeed, it’s actually planned to add a tooltip on the Apdex with more details about the numbers which caused this score (duration, origin of requests, etc..) so the precise time will also be an information to put in this tooltip.
-
Negative monitoring
I would like to have checks which fail when something is there which shouldn't be there. For example a http endpoint which should only be available through https.
13 votes -
Turn the webapp into a PWA (Progressive Web Application)
I believe the effort to turn you application into an webapp is pretty low (just include the manifest.json into the project root), and that would enable the users to install the website and use as an app.
It would also open some doors for future development:
- Send push notifications from web
- Offline access (yeah, this is kinda weird for you product)
- Improved caching
- Auto-updates straight from web (this is in comparison to native apps)6 votes -
Add support for Google Chat incoming webhooks
We would love to be able to post alerts to Google Chat using the incoming webhooks (cf. https://developers.google.com/hangouts/chat/how-tos/webhooks). A similar integration to the one already existing for Slack would be wonderful!
31 votes -
Multiple email addresses for the weekly report
I'd like to be able to enter multiple email addresses for the weekly report. For example, certain department managers would like to receive a weekly report of the checks, but not be disturbed every time a check goes up or down.
14 votes -
Time to first response
On the dashboard it would be nice to see the timing to the first response
18 votes -
Allow maintance window for planned IT jobs
Allow maintenance window for planned IT job (server down)
101 votesOk I'm moving this back to "under review" as it's gathering a lot of interest, but this would require first https://updown.uservoice.com/forums/177972/suggestions/16982392 and https://updown.uservoice.com/forums/177972/suggestions/15589635 to be implemented to provide a decent UI for this.
An alternative way to doing this now is to automate the check disable/mute on your end using the API, quite easy to do in a maintenance script: https://updown.io/doc/how-to-automate-check-disable
-
Group identical domain suffixes when ordering lexically
Right now I have about 20 subdomains across 3 top-level domains.
The current "domain-suffix-oblivious" lexical ordering is kind of a mess.
I really wish all my "hexstreamsoft.com" subdomains were grouped together, and same thing for my "hexstream.net" and "hexstream.xyz" subdomains separately. Right now those are all "randomly" jumbled up together based on the lexical order of their lowest subdomain components.
3 votes -
Provide pagerduty integration
Provide integration for https://www.pagerduty.com/
24 votesHi all, there’s now an option for that which is through Zapier (we just added native Zapier integration): https://updown.uservoice.com/knowledgebase/articles/1911991
Using this you can connect PagerDuty and receive alerts from updown.io. I’m keeping the suggestion “under review” because we might provide a native integration later.
-
Add UK location
The current 8 servers available are reasonably spread out, but it would be really great to include a UK server so I can see the experience of my UK audience.
I would also note that visitors from the middle-East and Africa don't get a look-in: perhaps something in Israel?
29 votes -
Custom CSS for Public Status Pagess
It would be nice to have either page specific or account wide custom stylesheet applied to the public status pages. Specifically, I'd use it to draw more attention to the translation dropdown and to eliminate some whitespace.
14 votes -
Longer History
Longer history than 30 days would be excellent for troubleshooting performance issues.
92 votes -
Better expired SSL certificate notifications
Notifications about expired certificates can be improved (made more noticable) in 2 ways:
1. Display expired certificates as downtime (or use some other highlighting) in weekly reports (and other periodic reports).
2. Send repeated notifications for expired certificates (as it is done for downtime).8 votes
- Don't see your idea?