Error Tracking Monitor

Overview

When Real User Monitoring or APM is enabled for your organization, you can create an Error Tracking monitor to alert you when an issue starts, 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

Choose Count to alert on issues with a high number of errors and New Issue to alert on issues that occur for the first time.

Define the search query

Select Web and Mobile Apps from the dropdown menu.

  1. 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.
  2. Construct a search query using the same logic as a RUM Explorer search for the issues’ error occurrences.

  3. Optionally, configure the alerting grouping strategy. For more information, see Monitor Configuration.

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.

The list of new issues might display older issues that are considered new in the selected time frame, such as the past 24 hours or the past week.

  1. 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.
  2. Select Web and Mobile Apps or Backend Services 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).
  3. Construct a search query using the same logic as a RUM Explorer search or APM Explorer search for the issues’ error occurrences.
  4. 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.

For more information about the Notify your team and Say what’s happening sections, see Notifications.

Further Reading