Skip to content

AdminAdrien Rey-Jarthon (Founder, updown.io)

My feedback

36 results found

  1. 62 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hi all, there's now two options for that which are:

    1. Through Zapier (we just added native Zapier integration): https://updown.uservoice.com/knowledgebase/articles/1911991  Using this you can connect pushover.net and receive alerts from updown.io. I'm keeping this suggestion "under review" to gather interest about a native integration with pushover.

    2. Using a DigitalOcean function to catch the webhook and push it to pushover (contributed by Marc): https://github.com/MarcHagen/function-updownio-to-pushover

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    Thanks Mark! I just added your function to the list of options.

  2. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    One important thing to note here is that having an invalid certificate does NOT prevent the expiration notifications. This is independent so you can keep an "invalid" certificate forever (updown will not notify you again about this) and still benefit from expiration warnings. This way we already kind of "tolerate" this use-case of running a non-publicly trusted certificate.


    About the suggested changes, I would like to avoid the custom cert/CA UI because that's a lot of added complexity for a very small use-case among my clients. It'll generate more support also as people will wonder what this do, try to upload other certificates, it'll be annoying for self-signed certificates, etc... The UI to manually "acknowledge" that one cert should be considered valid though sounds more doable for me, I'll keep this suggestion to track the demand and will probably add this someday.

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    Thanks @Javier, I made a longer reply by email but the TL;DR for people following this suggestion is that these websites not only use a custom CA cert, they also require TLS Client Certificates. So even implementing custom CA root cert would not be enough, and implementing also client certificates makes the endaevor quite bigger. The clients who needs this are very few and mostly enterprise which updown does not target. So I'm not gonna move ahead on this one, but I'm keeping the suggestion open to gather interest for later, and so I can notify you in case of changes.

    The "acknowledge" mentionned earlier might be implemented but it wouldn't help well in @Javier case and there's dozens of way to implement this so I'm still waiting for more occurences and experience before doing it.

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    Thanks for your feedback @Javier. Do you have some example websites and the associated CA public key so I can run some tests? You can send this to support@updown.io. Thanks.

  3. 12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    @Daz not that I am aware of. Feel free to give this a shot, if you make a working integration I can promote it here. Also let me know if you have any specific questions about the API.

  4. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    Why would you want that?

  5. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    Haha thank you Davyd, I am glad you find my product helpful :) I don't really want to spend time doing Youtube tutorials if that is what you're suggesting, but people are free to do some tutorials on using updown.io if they want !
    Although I doubt we can compete with this famous song ^^

  6. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    This is already possible, both single-side and multi-site status page have the X-Frame-Options header remove to permit iframe embedding. With the additional white-label mode to remove the logo if needed this works well. Are you having trouble with it?

  7. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    @Gautier unless I misunderstood something no they don't, even if you configure a custom domain, the check "Alias" or URL is displayed inside the page. The Alias already allows you to hide the URL and display something else instead, but what this suggestion is requesting is to have a different name shown for the public (e.g. like a "public alias") than the one shown privately in the dashboard.

  8. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    I suppose you meant "SSL" instead of "SSH"? (I updated the title). The SSL expiration alerts are already sent to the same email selected for check alerts (they do not support slack, telegram and others channels though..) so they are already following this configuration.
    The Domain expiration is not at the moment though (So if this is what you meant I agree it should probably follow the same alert emails).
    Could you please confirm if this is what you meant? your use-case? Thanks.

  9. 5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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 ☺

    I’ll mark this suggestion as “Under Review” to measure the need for this.

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    @Cilex when is OVH renewing?

  10. 7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    @Stefan thanks for commenting, the suggestion you are talking about (sometimes also called "pulse" or "cron" monitoring) is actually planned and tracked here: https://updown.uservoice.com/forums/177972-general/suggestions/5586072-periodic-task-cron-monitoring.

    The suggestion from Michael here is more about some kind of proxy daemon you could install so updown can access your private network "directly" (which is less likely to happen).

  11. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    +1 for iDeal

    AdminAdrien Rey-Jarthon (Founder, updown.io) supported this idea  · 
    AdminAdrien Rey-Jarthon (Founder, updown.io) shared this idea  · 
  12. 9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    Numbers like 5 sec will never be added because it needs to be a power of two (this is because we need to store the number of requests under ApdexT and ApdexT*4, so using power of 2 allows to reuse more numbers). So the next values that could be added without causing too much overhead are 4s and 8s. I'll update this suggestion to reflect this and leave it open to measure the interest.

  13. 100 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    Sorry but I can't give any ETA as this will depend on the time I have and other higher priority task that comes before. If you are hesitating on switching because of this I recommend staying with your current provider until you receive an update on the status of this suggestion. Or be prepared to keep both tools for a while.

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    Hello and thanks for your suggestion.

    The first option you're talking about where you would "refresh" the up status on your end is actually planned for later here: https://updown.uservoice.com/forums/177972-general/suggestions/5586072-periodic-task-cron-monitoring (under the name "pulse monitoring", "cron monitoring" and various other versions). I am actually gonna merge these suggestions together so you get the updates from the other suggestion and it adds up your vote too.

    Also as you said one alternative which is currently possible is to expose a small HTTP/TCP service to the outside for monitoring purpose only and configure this one in updown, some of our clients are doing this to "expose" the status of internal services. But I totally understand if you don't want to do this of course.

    In this case what I would recommend would be to use one of the existing pulse monitoring services discussed in https://updown.uservoice.com/forums/177972-general/suggestions/5586072-periodic-task-cron-monitoring before updown implements this, and once we do and if you want to consolidate everything in updown.io it should be easy to switch over.

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    Thanks for bringing this one to my attention, looks nice. I'm adding it to the list of alternatives in the description too so other people can use it.

    AdminAdrien Rey-Jarthon (Founder, updown.io) supported this idea  · 
    AdminAdrien Rey-Jarthon (Founder, updown.io) shared this idea  · 
  14. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    AdminAdrien Rey-Jarthon (Founder, updown.io) shared this idea  · 
  15. 12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

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

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    Yep, some of this will likely be added. Feel free to also upvote https://updown.uservoice.com/forums/177972/suggestions/33404443 and/or https://updown.uservoice.com/forums/177972/suggestions/39625915 for other options depending on what would be best for you.

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    Yes, thanks for the suggestion. I also think it may be interesting to only allow public status pages with custom domain (ex status.mywebsite.com) to be indexed and not the URLs on our domain (ex updown.io/ngg8). This way it keeps the client's website hostname visible and doesn't allow to list public pages in search. I'm not saying this a replacement for "hidden" status pages, more like an improvement for this initial suggestion. What do you think?

  16. 5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    What would be the use-case for this ? what would make it better than an hourly check for example ?

  17. 34 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    Ok, then feel free to create another suggestion because it's not the same thing that is asked here.

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    @Adrian that's a different case, this one is already possible by setting an "Alias" for your check.

  18. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    AdminAdrien Rey-Jarthon (Founder, updown.io) shared this idea  · 
  19. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    Thanks for the suggestion, indeed we didn't write such documentation because usually our users know when they are doing redirections but I understand it could be useful to some. I'll keep this idea open to measure interest.

  20. 11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    @Tony you can use https://tools.pingdom.com/ for example to get a waterfall view of the different redirection requests detailing how much time they took and from which URL you passed by.

    It's also possible with local tools like curl if you're familial with command-line (https://dev.to/yuyatakeyama/how-i-measure-response-times-of-web-apis-using-curl-6nh).

    An error occurred while saving the comment
    AdminAdrien Rey-Jarthon (Founder, updown.io) commented  · 

    Unfortunately the library we use to issue requests (libcurl) doesn't provide more detailed timings on the redirection intermediary requests, also presenting this amount of information would be much less readable so I don't think we'll do this but I'll keep the suggestion open to measure interest.

    Alternatively you can of course mesure the performance of your different redirections on your side and if you want to more detailed metrics from our locations you can contact us by email and I'll give them to you.

← Previous 1

Feedback and Knowledge Base