Update an error ingestion rule
Update the name, description, or filters of an error ingestion rule.
Restrictions
Usage
- Only fields present in the request are changed; omitted fields keep their current value.
- Calling update with no fields set is a no-op that still returns success.
- Returns
ResourceNotFoundifrule_iddoesn’t exist underapplication_id. - 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
Partial update to an existing error ingestion rule. Omitted fields are left unchanged.
RUM application ID. Get application IDs via POST /rum/application/list.
Rule ID to update. Get rule IDs via POST /rum/error-ingestion/rules/list.
New rule name, 1-128 characters. Omit to leave unchanged.
1 - 128New rule description, up to 512 characters. Omit to leave unchanged.
512New filter conditions. Omit to leave unchanged.
AND-group. The group only matches when every condition inside it matches.
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.