Error Tracking Monitors

Docs > Error Tracking > Error Tracking Monitors

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

Datadog Error Tracking automatically groups all your errors into issues across your web, mobile, and backend applications. Viewing errors grouped into issues helps you prioritize and find the problems that are most impactful, making it easier to minimize service downtimes and reduce user frustration.

With Error Tracking enabled for your organization, you can create an Error Tracking monitor to alert you when an issue in your web or mobile application, backend service, or logs is new, when it has a high impact, and when it starts regressing.

Create an Error Tracking monitor

To create an Error Tracking monitor in Datadog, navigate to Monitors > New Monitor > Error Tracking.

Note: There is a default limit of 1000 Error Tracking monitors per account. Contact Support to increase this limit for your account.

Select the alerting condition

There are two types of alerting conditions you can configure your Error Tracking monitor with:

Alerting condition	Description
High Impact	Alert on issues with a high number of impacted end users. For example, alert for your service whenever more than 500 users are impacted by this error.
New Issue	Alert when an issue occurs for the first time. You have the option to be notified if a regression occurs, and set a threshold to reduce alerting fatigue.

Define the search query

Select RUM Events, Traces, or Logs from the dropdown menu and choose what metric you want to monitor: a count, facet, or measure.
- For error occurrences, monitor over an overall count based on the issue ID.
- For impacted users, monitor over a unique count of user emails based on the issue ID or over a measure.
- For impacted sessions, monitor over a unique count of session IDs based on the issue ID.
- Monitor over a measure. If you select a measure, the monitor alerts over the numerical value of the RUM facet (similar to a metric monitor). Select an aggregation type (min, avg, sum, median, pc75, pc90, pc95, pc98, pc99, or max).
There are three quickfilter options to access the most frequently used facets:
- Error Occurrences: Triggers when the error count is above or above or equal to.
- Impacted Users: Triggers when the number of impacted user emails is above or above or equal to.
- Impacted Sessions: Triggers when the number of impacted session IDs is above or above or equal to.
If you select Traces or Logs from the dropdown menu, only the Error Occurrences option is available.
Construct a search query using the same logic as a RUM Explorer search, APM Explorer search, or Log Explorer search for the issues’ error occurrences.
Optionally, configure the alerting grouping strategy. For more information, see Monitor Configuration.

Note: Count monitors for APM can only be created based on spans retained by custom retention filters (not the intelligent retention filter).

Set alert conditions

Triggers when the error count is above or above or equal to. An alert is triggered whenever a metric crosses a threshold.

Select or input a custom time period for the monitor to consider an issue as new after its first occurrence. The selected threshold is evaluated in the given time frame. After the specific time period, the monitor stops alerting and turns green.
The list of issues on top has a separate time frame selector. It can be used to find which issues would be considered new in this time frame.
Select RUM Events, Traces, or Logs and choose to monitor over a count or measure.
- Monitor the count of occurrences for a specific issue ID.
- Monitor over a measure. If you select a measure, the monitor alerts over the numerical value of the RUM or APM facet (similar to a metric monitor). Select an aggregation type (min, avg, sum, median, pc75, pc90, pc95, pc98, pc99, or max).
Construct a search query using the same logic as a RUM Explorer search, APM Explorer search, or Log Explorer search for the issues’ error occurrences.
Optionally, configure the alerting grouping strategy. For more information, see Monitor Configuration.

Set alert conditions

The monitor triggers when the number of errors is above or above or equal to.

Set a timespan between 5 minutes and 48 hours (such as 5 minutes, 15 minutes. 1 hour, or custom) over which the monitor metric is evaluated.
Set the alerting threshold > <NUMBER>.
Set the warning threshold > <NUMBER>.

Advanced Alert Conditions

For more information about advanced alert options such as evaluation frequency, see Configure Monitors.

Notifications

To display triggering tags in the notification title, click Include triggering tags in notification title.

In addition to matching attribute variables, the following Error Tracking specific variables are available for alert message notifications:

{{issue.attributes.error.type}}
{{issue.attributes.error.message}}
{{issue.attributes.error.stack}}
{{issue.attributes.error.file}}
{{issue.attributes.error.is_crash}}
{{issue.attributes.error.category}}
{{issue.attributes.error.handling}}

For more information about the Configure notifications and automations section, see Notifications.

Muting monitors

Error Tracking monitors use Issue States to ensure that your alerts stay focused on high-priority matters, reducing distractions from non-critical issues.

Ignored issues are errors requiring no additional investigation or action. By marking issues as Ignored, these issues are automatically muted from monitor notifications.