Skip to content

Manuel

My feedback

6 results found

  1. 6 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)
  2. 8 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)
  3. 148 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)

    Hello everyone, I’ve just added a way to get the detailed results from the last 5 checks before downtime and recovery to the downtime API, all you have to do is add the “results=true” parameter, like this:

    https://updown.io/api/checks/yyyy/downtimes?api-key=xxxxxxxxxxxxxx&results=true

    Warnings:
    - This API is alpha version, it can still change.
    - The response can be huge, I recommend using this only when needed and with http gzip compression if you can.
    - The dual stack results (IPv4 and IPv6) will NOT repeat “body” and “received_headers” if they are the same as in the parent result record, to save space.

    Let me know what you think!

  4. 148 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 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)

    This was planned for a while because initially with only the individual status pages there was no way to specify any text. But now that we have the multi-site status pages (e.g. https://demo.updown.io/), there is a free text "description" at the top, which supports links, newlines and emojis. This allows for this kind of use-case (roughly) as you can edit this field to indicate incidents, times, some emoji to catch attention on current status, link for more details, etc..


    Now that we have this, I prefer to wait before implementing more specific status page features because we don't really want to become a full-fledged status page provider otherwise people will ask for MUCH more (notifications to clients, RSS, integrating other metrics, custom design, etc..) and we have enough work to spend our time on the core product (the monitoring) already ☺

  5. 16 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)
    Manuel supported this idea  · 
  6. 352 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 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)

    This is not something I have plans for in the near future because of the complexity and the wide other range of feature requests it would attract due to bigger clients (permissions, roles, audit logs, SSO, SLA, etc...). But I might do it at some point if I want to target bigger clients.

    Manuel supported this idea  · 

Feedback and Knowledge Base