bulk_update_monitors

sh.fettle/mcp · Verify this server

Set the same values on up to 100 monitors in one call, all or nothing, for example move twenty PING monitors to other regions or a slower interval. Requires a key with the write scope. monitor_ids (array of 1 to 100 distinct monitor uuids, required; an unknown id is a 404 naming it, a repeated id a 422). changes (object, required) holds one or more of: interval_seconds (30 to 86400), timeout_seconds (1 to 120), regions (list of region codes; see list_regions), channel_ids (array of channel uuids from list_channels; replaces each monitor's binding, [] clears it, an unknown channel is a 404), confirmation_threshold (1 to 10) and notification_cooldown_seconds (60 to 86400). Omit a field to keep it; never send null. config, name and tags are not here: use update_monitor or bulk_update_monitor_tags. The plan's rules apply to the result: an interval below the plan minimum, too many fast-interval monitors, more regions than allowed or an unknown region is a 403. A value one monitor cannot take (an SSL or DNS monitor with more than one region; a port-list TCP monitor with several regions or an interval under 300) is a 422 that starts with monitors[<i>] ("<name>"). Returns monitors: short rows (id, name, type, target, status, is_active, tags, interval_seconds, ssl_expires_at, last_checked_at), so they show the interval but not the other changed settings; get_monitor gives a monitor's full settings. Example: {"monitor_ids": ["<id from list_monitors>", "<id from list_monitors>"], "changes": {"regions": ["eu-central", "us-east"], "interval_seconds": 300}}