Suspect Commits

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.


Error Tracking can identify suspect commits, helping you pinpoint the root cause of your errors and expedite resolution. This feature is automatically enabled on issues when the setup requirements are met.

A suspect commit as it is displayed in the Datadog UI

Once a suspect commit has been identified, it is displayed on the issue panel, as shown in the highlighted area of the image below.

A suspect commit shown in the context of the issue panel

To view a suspect commit on GitHub, click the View Commit button.

Suspect commit criteria

A commit becomes a suspect commit if:

  • It modifies one of the lines in the stack trace.
  • It was authored before the first error occurrence.
  • It was authored no more than 90 days before the first error occurrence.
  • It is the most recent commit that meets the above criteria.

For a suspect commit to be displayed on an issue, at least one candidate commit must have been found.


Once the setup requirements are met, suspect commits automatically appear on issues where available. Commits made before the setup requirements were met are not displayed.

Enable Source Code Integration

The Suspect Commits feature requires Source Code Integration. To enable Source Code Integration:

  1. On the Integrations page in Datadog, choose Link Source Code in the top navbar.
  2. Follow the steps to associate a commit with your telemetry and configure your GitHub repository.

Install the GitHub integration

Install the GitHub integration, enabling read permissions for pull requests and contents.