Investigate Errors with Bits AI

This product is not supported for your selected Datadog site. ().
Preview

Bits Investigation in Error Tracking is in Preview.

Overview

Bits Investigation is an autonomous AI agent that investigates production issues. When you start an investigation from an Error Tracking issue, Bits analyzes the error, including its stack trace and related telemetry. If you set up Source Code Integration, Bits also analyzes your source code. It then reports the likely root cause and the impact of the issue.

To list all investigations triggered from Error Tracking, open Investigations and filter on Source: Error Tracking Issue.

Prerequisites

Investigate an Error Tracking issue

To investigate an Error Tracking issue with Bits Investigation:

  1. In the Error Tracking Explorer, click an issue to open the issue panel.

  2. On the Review tab, click Investigate this issue in the Bits Investigation banner.

    The Bits Investigation banner on the Review tab of an Error Tracking issue, with the Investigate this issue button.

    While the investigation runs, the banner shows its progress and who triggered it. An investigation usually takes a few minutes.

  3. When the investigation completes, review the findings in the banner:

    • Root cause: The most likely cause of the error, based on the evidence Bits gathered.
    • Impact: How the error affects your users and services.

    For a completed investigation, the banner displays the root cause and impact side by side:

    The Review tab of an Error Tracking issue, showing the root cause and impact found by Bits Investigation.

    If the available data is insufficient to support a conclusion, Bits marks the investigation as inconclusive.

  4. (Optional) To see the full investigation, click View Investigation in the banner.

    The investigation page shows the conclusion, suggested next steps, and a timeline of the evidence:

    The Bits Investigation page for an Error Tracking issue, showing the conclusion, root cause, impact, a suggested next step, and the timeline.

To ask follow-up questions about the investigation, use Bits Chat. For more information, see Chat with Bits Investigation.

For more information about how Bits reaches its conclusion and how to explore the investigation steps, see How Bits investigates in Investigate Issues.

Fix the issue in code

When the root cause is in your code, Bits Investigation uses Bits Code to generate a fix. The fix appears as a suggested next step on the investigation page, with a summary of the change and its diff.

A code fix next step includes actions to open a pull request or keep working on the fix:

A suggested next step with a code fix generated by Bits Code, showing a summary, a diff, and the Create PR and View in Bits Code buttons.

From the next step, you can:

  • Click Create PR to open a pull request with the fix.
  • Click View Full Diff to review all changed files.
  • Click View in Bits Code to iterate on the fix in a Bits Code session.

Bits Code never merges changes automatically. Review and test generated code before you merge it.

Further reading