General

  1. 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 monitoring

    0 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 →

    Hello,

    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 ☺

  2. 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 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. SLOs and SLA for updown.io itself

    More SLO's and SLA's for uptown.io itself. In exchange for more $.

    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 →

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

  4. 1 ping par jour

    Ping une seule fois par jour, a une heure precise

    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 →
  5. Allow maintance window for planned IT jobs

    Allow maintenance window for planned IT job (server down)

    37 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 →

    This is not planned currently as it would allow to fake number too easily but If you want to hide maintenance windows, you can disable your check before and re-enable it after. (can be automated using the API from a maintenance scripts or cron).

  6. Higher timeout threshold

    We have a couple of long running dashboard pages and a higher timeout threshold would be useful

    3 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 →
  7. Organizations / teams

    Organizations - I would like to group some checks into organizations with their own settings (billing / members / notifications / webhook / API / etc..)

    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 →

    If you want everything to be separate (even billing), just create multiple accounts. You can already configure notification channels per check (email, sms, slack, webhook) but we won’t make it possible to split everything as you wish.

  8. 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, 1h

    My "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…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. More heck periods: 2h and 4h

    More check intervals: 2h, 4h.

    2 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 →
  10. Support larger subset of response codes

    An api might return a 503 status to indicate it is in maintence mode, it would be nice to be able to check for a subset of response codes rather than just 200 OK

    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 →

    The string search features allows to match on a text instead of a status, this is useful for testing special status responses. And a 503 (if properly used for maintenance) should be considered down, if you want to hide the downtime caused by maintenance from updown.io you need to disable the check before the maintenance.

  11. More apdex values: 1.5s and 2.5s

    Perhaps I'm missing something, but I interpret the apdex time value you configure for a site as the desired maximum response time for the site. If this is so, it seems odd that it maxes out at 2s. While a commercial site might be able to afford the hw to get it below 1s easily, not everyone can.

    So, could we have a little more granularity in the 1s to 2s region?

    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 →

    Most website can easily respond in less than 0.5s even if queries from the other half of the world. We initially supported only up to 1s and added 2s later but we don’t want to encourage people into thinking 2s+ response time is acceptable so we won’t go higher. If your website is slower and this is acceptable to you it’ll of course monitor properly, but you’re not gonna be able to show an all green Apdex score.

  12. Please. Show the prom size in KB

    Slow responses can be caused by big pages (urls). If I have idea of this then I can do something more.

    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 →

    No it can’t because we measure the time it takes until your server starts responding, not until we finished downloading the body. And we don’t download any body by default anyway as we use the HEAD http verb, only when you use the string search feature. So the page size is irrelevant to this measure.

  13. Create WHMCS Module For Selling and Displaying Uptime In WHMCS Client Accounts

    I love updown.io, but UptimeRobot has got WHMCS dialed in. You guys should get in that game. Make a module that allows us to display updown uptime monitoring in the WHMCS client area. Not sure where you guys are in the as far as the reseller market goes, but you can also add functionality for reselling your service to our WHMCS clients and make bank. Think of how much more exposure that would be.

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

    I see a weekly report, but I would love to see a monthly one as well. Many people have to report up a final number and this would save me doing some math every month. I basically just need the uptime percentage for the entire month.

    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 →
  15. return code

    Include workflow-kind tests the ability to check HTTP return codes and POSTs for submitting forms.

    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. Chicago Monitor Location

    How about adding a chicago monitor location? Our company is based in Chicago and most of our clients are based here. The response time from LA and Miami are slow.

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

    Response time does not impact monitoring, it’s normal to have slower response time from further away locations. But in your case the latency from SF and Miami to Chicago is very small (<10ms) so the performance issue your are seeing is all on your side.

  17. 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 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 →

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

  18. Javascript browser tests

    It would be cool to have more advanced browser tests that could test javascript.

    It already happened to me that my javascript file couldn't be loaded (come cache issue) which resulted in an unusable website until we realized the javascript had crashed and all menus were unuseable.

    Some services can scripted browser tests so we can verify some javascript interactions actually work. Would love to see that on your app.

    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 →

    Unfortunately this is much more expensive and super unreliable so we’ll never use it for the main monitoring. Though at some point we may add some side features to try your website in a browser from time to time and let you know if it breaks for some reason but that’ll only be warning notifications (like we do with SSL alerts).
    And most importantly it won’t be configurable, as this would require a very complex setup which is not in the updown.io philosophy

  19. 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 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 →

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

  20. Add notes about downtime incident

    I'd love to be able to add a note to each downtime notice, so months later if a client complains I can accurately say "That was when AWS went down" or "That was because your developer wipes the site by mistake" :)

    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 →
← Previous 1 3
  • Don't see your idea?

General

Categories

Feedback and Knowledge Base