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.
Exception Replay for APM Error Tracking is in beta.


Exception Replay in APM Error Tracking automatically captures production variable values so you can reproduce exceptions from Error Tracking issues.

Error Tracking Explorer Exception Replay


Supported languages
  • Your Datadog Agent must be configured for APM.
  • Your application must be instrumented with ddtrace.

Exception Replay is only available in APM Error Tracking. Error Tracking for Logs and RUM is not supported.


  1. Install or upgrade your Agent to version 7.44.0 or higher.
  2. Ensure that you are using ddtrace version 1.16.0 or higher.
  3. Set the DD_EXCEPTION_DEBUGGING_ENABLED environment variable to true to run your service with Error Tracking Exception Replay enabled.

Redacting sensitive data

By default, variable data linked to specific identifiers deemed sensitive, such as password and accessToken, are automatically redacted. See the full list of redacted identifiers.

You can also scrub variable data for PII by:

To learn more about scrubbing variable data, see Dynamic Instrumentation Sensitive Data Scrubbing.

Getting started

  1. Navigate to APM > Error Tracking.
  2. Click into any Python Error Tracking issue and scroll down to the stack trace component.
  3. Expand stack frames to examine captured variable values.


A specific Python error trace does not have variable values

To keep the performance overhead of the feature at a minimum, error capturing is rate limited: one error per second includes variable data. If you don’t see variable values on a given trace:

  1. Click View Similar Errors.
  2. Expand the time range selection to find another instance of the exception where variable values were captured.

Further Reading