Skip to content

Martijn

My feedback

1 result found

  1. 101 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Ok I'm moving this back to "under review" as it's gathering a lot of interest, but this would require first https://updown.uservoice.com/forums/177972/suggestions/16982392 and https://updown.uservoice.com/forums/177972/suggestions/15589635 to be implemented to provide a decent UI for this.


    An alternative way to doing this now is to automate the check disable/mute on your end using the API, quite easy to do in a maintenance script: https://updown.io/doc/how-to-automate-check-disable

    An error occurred while saving the comment
    Martijn commented  · 

    For the meanwhile, you can easily fix this using the API ( https://updown.io/api ):
    1. Get all your checks using https://updown.io/api/checks?api-key=:api_key
    2. Loop through them and call
    curl -X PUT -d 'enabled=false' https://updown.io/api/checks/:token?api-key=:api_key
    to disable them.
    3. To re-enable, repeat step 2 with enabled=true.

    This is a simple example, you can easily extend this by only handling checks that weren't disabled before, or you can run this on set times using a cron job if you have a set maintenance window.

Feedback and Knowledge Base