General

  1. servers in hong kong and indonesia

    servers in hong kong and indonesia

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow URLs with non-ascii symbols

    Allow monitoring a URL suck as http://wikipedia.org/wiki/λ or http://wikipedia.org/wiki/🍔. It's annoying to manually have to URL-encode URLs and it's hard to see what the “real” URL is in the list when it's all percentage signs and numbers.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add Belgium location

    Add more server locations ( in particular Belgium)

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. Include small response body in notifications directly

    I typically implement a health check/status endpoint in my services, so it will return both a JSON response, and a valid HTTP status code (eg. 200 on success, 500 on error, for example).

    Thing is, when I use this in combination with updown.io, I only get notifications that specify the reason based on the error code, eg. "Internal Server Error".

    What I'd really want here is to have at least the Slack notifications include the entire response, or even just part of the response.

    I'd even be fine if it only worked like this when you use the "contains" functionality,…

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Hello and thank you for the suggestion. Doing special treatment for monitoring endpoints (versus website pages) is too specific and error-prone so we’re not gonna do that.

    One thing which might be done to help in this case is display the response body when using the contains feature but this only makes sense if it’s small and simple (no html). How does yours look?

  6. 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.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. @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
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Uptime Reports for month, year

    Get Uptime report for the whole year

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Indeed, 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.

  10. 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…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  11. Add the ability to disable following redirects

    Currently updown.io will follow 302 redirects when checking if a service is up. In the `curl` commands that are emailed when downtime is detected, this is achieved via the `-L` flag. It would be good if this could be disabled, so that the actual endpoint given is tested and not the endpoint at the end of the 302(s).

    An example of when this might be useful: I have a few endpoints that simply 302 to another endpoint, which I don't maintain / own / have any control over. I'm less interested in whether those endpoints are up, and more interested…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. explicit DNS checks

    The current monitoring seems to use resolvers with "hot" caches - hot means they are populated already by the periodic checks.
    For many of ay checks this leads to a DNS resolution time of 0.

    What would be good is a check which does the resolution from the start (root-servers) and implements the whole resolution process itself.

    These kind of checks are resource intensive so they should be limited to every 5 minutes or so.

    Additionally the whole dns resolution paths could be investigated like dnstrace by D.J. Bernstein does (dnstrace/dnstracesort are part of the tinydns package).

    This doesn't fit…

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add name to phone numbers

    Give a name to phone numbers! otherwise it's hard to know who they belong to.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Google Sheets Integration

    Google Sheets integration.
    We use the API now with an external Python script polling in data every x minutes to keep our overviews up to date.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Bulk switch apdex level

    Bulk option: change the apdex time level, e.g., quickly switch between .5 seconds and 1 second to see difference.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. 0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. More Bulk Options

    It would be useful to have bulk editing options for the "check interval" and "monitoring locations".

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5
  • Don't see your idea?

General

Categories

Feedback and Knowledge Base