Update preset severity rule
Update the name, description, filters, or severity of a preset severity rule.
Restrictions
Usage
- Only fields present in the request are changed; omitted fields keep their current value.
- Returns
ResourceNotFoundifrule_iddoes not exist in the application. - If
filtersis provided it replaces the entire filter structure and is revalidated against the same allowed key set ascreate. - Every call is recorded in the account audit log. Don’t put secrets in request fields.
Authorizations
App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.
Body
Parameters for updating a preset severity rule. Only provided fields are changed.
RUM application ID. Get application IDs via POST /rum/application/list.
Rule ID to update. Get rule IDs via POST /rum/issue/preset-severity/rules/list.
New display name, 1-128 characters. Omit to leave unchanged.
1 - 128New description, up to 512 characters. Omit to leave unchanged.
512OR-of-ANDs filter structure: the outer array is OR'd, each inner array is AND'd. A rule matches an error when at least one inner AND-group fully matches.
New severity. Omit to leave unchanged.
Critical, Warning, Info Response
Success
Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.