Skip to content

SuitePad GmbH

← updown.io feedback

My feedback

4 results found

  1. Allow custom headers in webhook requests

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close
    SuitePad GmbH supported this idea  · 

  2. Custom CSS for Public Status Pagess

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close
    SuitePad GmbH supported this idea  · 
    An error occurred while saving the comment
    SuitePad GmbH commented  · 

    @adrien Ah! Sorry, I just noticed your response from April.

    I'd mostly try to offload the risk of breaking desings to the user. You could add a version class - "version-1.23" to the body tag. Then users could structure their CSS with the version tag and new pages would just look like the default theme. Best case: users are warned so they understand the risk and get a heads up that new dom version is coming.

    I do think that there is too much white space above the "last 24 hours". Otherwise, I actually think it is a really nice page. If I had custom CSS, I would:

    1. Add company logo, if I could find a way to do it tastefully.
    2. use some company colors, where it makes sense
    3. limit white space, possibly try to use flexbox to put locale selection and the check title in one row.

    SuitePad GmbH shared this idea  · 

  3. Allow maintance window for planned IT jobs

    92 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    14 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)
    Close
    Close
    SuitePad GmbH supported this idea  · 

  4. Log of uptime/downtime

    141 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close
    started  ·  AdminAdrien Rey-Jarthon (Founder, updown.io) responded

    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!

    An error occurred while saving the comment
    SuitePad GmbH commented  · 

    I'm particularly eager to find a way to get a list of recent pings, the same as in the email. It would be ideal if I could click from the dashboard/index page of all my checks into individual request histories. The link I'm looking for is: http://updown.io/downtimes/590a04fc18b2ad5dcc225f5a/results/590a063ecbce6b27d2ad7fb0

    SuitePad GmbH supported this idea  · 

Feedback and Knowledge Base

(thinking…)