Glitches

Create one glitch rule for this project.

The tenant decides what counts as a glitch for their own app. action: "ignore" suppresses matching observations; action: "track" records them under label (the tenant's own category name, which becomes the group key, class custom) with an optional tenant-authored remediation hint. At most 50 rules per project; at most 32 statuses per rule; path_prefix must start with /; host is a bare hostname. Rules apply within a minute, and only affect FUTURE observations.

Requires the glitches:write scope and a project-scoped credential.

post/v1/glitches/rules

Request

  • Base URL: https://api.scalix.world
  • URL: https://api.scalix.world/v1/glitches/rules
  • Auth: HTTP bearer

Request body

actionstring required

ignore (never a glitch for my app) or track (record under my label).

labelstring nullable

Required for track: the tenant's own category name (becomes the group key, 1-64 chars).

hintstring nullable

Optional: the tenant's own remediation note shown with the group (max 280 chars).

match_statusesinteger[] required

HTTP status codes this rule matches (100-599, 1-32 codes).

path_prefixstring nullable

Optional path prefix the rule is scoped to (must start with /, max 256 chars).

hoststring nullable

Optional exact host the rule is scoped to (bare hostname, max 253 chars).

Response

Rule created

Changes

No recorded changes to this operation across all 1 revision of this API.