Reconfigure one platform alert condition

Replaces the tunable configuration of one seeded condition: whether it is evaluated,
its threshold, its dwell and its cooldown.

The condition KEY and its SEVERITY are not settable. A settable severity would let a
destination's severity filter be bypassed by editing the condition instead of the
destination — the same authorization decision expressed in two places, which is how
the two come to disagree.

Disabling a condition that is currently FIRING closes it: resolved_at is set and one
RESOLVED notification is emitted. Left open it would sit firing in the console forever,
because nothing evaluates it any more.

Authorization: admin.platform.alerts.write.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
Body Params

Reconfigures a seeded alert condition. The key and severity are fixed.

boolean
required

Whether this condition is evaluated.

number
0.0001 to 1

Ratio threshold in (0,1]. Absent for a state condition.

int32
required
0 to 86400

Continuous dwell before firing, in seconds.

int32
required
60 to 2592000

Minimum interval between notifications while firing, in seconds.

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json