Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel,
n'hésitez pas à nous contacter.
Overview
On-call processing rules allow teams to customize their response strategies for distinct types of incoming events. This enables teams to add events and urgency levels to escalation policies based on the event’s metadata. Low urgency pages do not trigger escalation processes.
Datadog creates a default processing rule when you onboard a Team to On-Call.
View your team’s processing rules
To see the processing rule of your On-Call Team, click on the Team name in the list of Teams.
Query syntax
Processing rules follow the common query syntax of Datadog. Supported attributes include:
tags: the tags set on the incoming alert. For example, tags.env:prod.groups: checks if the incoming alert relates to a specific Monitor group. For example, groups:"service:checkout-service".priority: value of the priority field of the Monitor. Possible values include 1, 2, 3, 4, or 5. For instance, priority:(1 OR 2).alert_status: value of the Monitor’s status. Possible values include error, warn, success. Usage example: alert_status:(error OR warn).
If no specific filter should be applied, use *.
Ordering
The ordering of processing rules matters. The system goes from top to bottom and stops at the first matching rule. If no query or time filter matches the incoming alert, the default processing rule is used.
Further reading
Documentation, liens et articles supplémentaires utiles:
