Error Tracking for Logs

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.


It is critical for your system’s health to consistently monitor the errors collected by Datadog. When there are many individual error events, it becomes hard to prioritize errors for troubleshooting. By tracking, triaging, and debugging logs, you can minimize the impact of fatal errors on your browser, mobile, and backend services.

Once you have set up Logs for Browser and Mobile or Backend error tracking, the issue list populates with cards. Navigate to Logs > Error Tracking to view open, ignored, or all issues, sort issues by volume or age, and filter issues by all custom and default facets on your logs.

The Error Tracking Explorer for Logs displaying Java issues

Error Tracking enables you to:

  • Set monitors on error tracking events such as high error volumes or new issues introduced.
  • Group similar errors into issues, so that you can more easily identify important errors and reduce noise.
  • Follow issues over time to know when they first started, if they are still ongoing, and how often they are occurring.
  • Collect all the necessary context in one place to facilitate troubleshooting.


Error Tracking for Logs processes properly configured error logs with stack traces.

To get started with Datadog Error Tracking for Logs, see the corresponding documentation for your framework:

Investigate issues and start triaging

An issue is a grouping of any number of errors based on a fingerprinting algorithm that groups certain error logs with required attributes like a stack trace.

A sidepanel consisting of details of a log error

Click on an issue to see seasonality patterns, a stack trace, and the error’s distribution across env and version tags. The issue panel displays the first and last versions impacted with timestamps.

Further Reading