Error Tracking for Backend Services


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 stack traces, you can minimize the impact of fatal errors on your backend services.

Once you have set up APM for Backend Services error tracking, the issue list populates with cards. You can view open, ignored, or all issues, sort issues by volume or age, and filter issues by all custom and default facets on your backend services.

The Error Tracking Explorer for APM displaying issues from your backend services

Error Tracking enables you to:

  • Set alerts on Error Tracking events. This helps you to remain informed of fatal issues that may occur.
  • 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.

Use span tags to track error spans

Error Tracking is available for all the languages supported by APM and does not require using a different SDK.

The Datadog tracers collect errors through integrations and the manual instrumentation of your backend services’ source code. Error spans within a trace are processed by Error Tracking if the error is located in a service entry span (the uppermost service span). This span must also contain the error.stack, error.message, and error.type span tags to be tracked.

Flame graph with errors

Error Tracking computes a fingerprint for each error span it processes using the error type, the error message, and the frames that form the stack trace. Errors with the same fingerprint are grouped together and belong to the same issue. For more information, see the Trace Explorer documentation.

Examine issues to start troubleshooting or debugging

Error Tracking automatically categorizes errors into issues collected from your backend services in the Error Tracking Explorer.

Click on an issue to see a summary of the error, the distribution of impacted spans, the latest most relevant stack trace, span tags, host tags, container tags, and metrics.

Further Reading