Skip to main content
POST
Create an error ingestion rule

Restrictions

Usage

  • A matched error is still stored and queryable, but is not grouped into any issue, and its issue_grouping_excluded field is set to true.
  • Rules are matched against the error’s raw type and message as reported by the SDK, before the server parses the stack trace.
  • Every condition key in filters must be one of the supported error.* fields or a context.* path; unsupported keys, unknown operators, empty vals, or invalid regexp/CIDR/number patterns return InvalidParameter.
  • New rules start with status enabled; call disable afterward if the rule should start inactive.
  • Each write first saves the application’s whole rule set, as it was before the change, as a new history version.
  • Ingestion reads enabled rules from a per-application cache that lives 5 seconds, so the change applies to newly ingested errors within about 5 seconds.
  • Requires edit access to the application (account owner or admin, the application’s creator, or a member of its team); otherwise returns AccessDenied. An unknown application_id returns ResourceNotFound.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Fields for creating a new error ingestion rule.

application_id
string
required

RUM application ID. Get application IDs via POST /rum/application/list.

filters
object[][]
required

Conditions (OR-of-ANDs) that select errors. A matched error is still stored but is not grouped into any issue.

AND-group. The group only matches when every condition inside it matches.

rule_name
string
required

Rule name, 1-128 characters.

Required string length: 1 - 128
description
string

Rule description, up to 512 characters. Defaults to an empty string.

Maximum string length: 512

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.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object

The newly created rule's identity.