Create Ignore Rule
create_ignore_ruleIgnore rules exclude a traffic fingerprint (e.g. HTTP 404 responses, or one client address) from burn-rate alert evaluation for a service/operation. This changes the data that counts toward error/latency burn — it does not mute notifications. To temporarily silence alert notifications without changing evaluation, use suppress_signal instead. Also created from the 'Ignore this pattern' button on an alert; button-created rules expire after a configured period (90 days by default) and can be made permanent from the confirmation page. WRITE: requires the ADMIN role.
A rule masks matching traffic from ONE signal's burn evaluation only — set signal to ERROR_RATE or LATENCY_P95. URL_PATH values are matched against normalized paths ({id} segments), so pass the template form (e.g. /orders/{id}); raw ids are normalized automatically.
Scope: signal: required (ERROR_RATE or LATENCY_P95). THROUGHPUT has no burn evaluation. service: required. operation: optional. Omit to ignore the fingerprint across the whole service. Required for LATENCY_P95 (service-level latency is not re-evaluated, so the rule would do nothing). dimension: which fingerprint attribute to match (e.g. HTTP_STATUS, CLIENT_ADDRESS, URL_PATH). value: the attribute value to ignore.
Duration: expiresInHours: optional. Omit for a permanent rule.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| value | Yes | The fingerprint value to ignore (URL_PATH values are normalized) | |
| signal | Yes | Signal to mask: ERROR_RATE or LATENCY_P95 | |
| service | Yes | Service name the rule applies to | |
| dimension | Yes | Fingerprint dimension to match: one of CLIENT_ADDRESS, END_CUSTOMER, USER_AGENT, URL_PATH, MESSAGING_DESTINATION, DB_STATEMENT, GENAI_MODEL, TARGET_HOST, HTTP_STATUS | |
| operation | No | Operation to scope the rule to. Omit for the whole service (not allowed for LATENCY_P95) | |
| expiresInHours | No | Hours until the rule expires. Omit for a permanent rule |