From 0b715992c96f0054efdd4b2e55c0e5e688cf05c0 Mon Sep 17 00:00:00 2001 From: ThibaultK Date: Thu, 11 Jun 2026 15:50:22 +0200 Subject: [PATCH 1/4] Add Error Tracking Bits Investigation docs page New ET page for Bits Investigation (manual investigation: root cause, impact, suspect commits, next steps) and the handoff to Bits Code for code fixes. Replaces the ET nav's Bits Code link; Bits Code stays reachable from the Bits AI menu and is linked in-context. Documented as in trial, no pricing content. Screenshots and a few exact labels left as TODO. --- config/_default/menus/main.en.yaml | 6 +- .../en/error_tracking/bits_investigation.md | 130 ++++++++++++++++++ 2 files changed, 133 insertions(+), 3 deletions(-) create mode 100644 content/en/error_tracking/bits_investigation.md diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml index 04111ed6c43..57b24f138d1 100644 --- a/config/_default/menus/main.en.yaml +++ b/config/_default/menus/main.en.yaml @@ -2330,10 +2330,10 @@ menu: parent: error_tracking identifier: error_tracking_error_grouping weight: 4 - - name: Bits Code - url: bits_ai/bits_ai_dev_agent + - name: Bits Investigation + url: error_tracking/bits_investigation parent: error_tracking - identifier: error_tracking_bits_ai_dev_agent + identifier: error_tracking_bits_investigation weight: 5 - name: Monitors url: error_tracking/monitors diff --git a/content/en/error_tracking/bits_investigation.md b/content/en/error_tracking/bits_investigation.md new file mode 100644 index 00000000000..3fbd0c969e5 --- /dev/null +++ b/content/en/error_tracking/bits_investigation.md @@ -0,0 +1,130 @@ +--- +title: Bits Investigation +description: Investigate Error Tracking issues with Bits Investigation to find the root cause, assess impact, and hand off a code fix to Bits Code. +further_reading: +- link: '/bits_ai/bits_ai_dev_agent/' + tag: 'Documentation' + text: 'Generate code fixes with Bits Code' +- link: '/integrations/guide/source-code-integration/' + tag: 'Documentation' + text: 'Set up Source Code Integration' +- link: '/error_tracking/link_pull_requests/' + tag: 'Documentation' + text: 'Link pull requests to issues' +- link: '/error_tracking/issue_states/' + tag: 'Documentation' + text: 'Manage issue states' +- link: '/bits_ai/bits_ai_sre/' + tag: 'Documentation' + text: 'Bits Investigation for alerts and monitors (on-call)' +--- + +
Bits Investigation in Error Tracking is in trial. Behavior and availability can change, and the product shows a trial badge while the trial is active.
+ +## Overview + +Bits Investigation is built into Error Tracking. When you open an issue, it investigates the error and reports the likely root cause, who and what is affected, and the recommended next step. When the resolution is a code change, it hands off to [Bits Code][1] to generate the fix. + +This page covers Bits Investigation in Error Tracking. To investigate alerts and monitors during on-call, see [Bits Investigation for on-call operations][2]. + + + +## How it works + +You start an investigation from the issue side panel. Bits Investigation then: + +1. Reads the issue, including the stack trace, error attributes, and related telemetry (logs, traces, and RUM events). +2. Reads the relevant source code when [Source Code Integration](#connect-your-source-code) is set up. +3. Forms a hypothesis about the root cause and checks it against the available data. +4. Returns a result: the root cause, an impact assessment, suspect commits, and a recommended next step. + +From the result, you decide what to do next: generate a code fix with Bits Code, copy the context into your own AI assistant, create a ticket, or resolve or ignore the issue. + +When source code is not connected, the investigation still runs but works from error patterns and telemetry only, so the result has less detail. The side panel marks these results so you know the investigation ran with reduced context. + +## Prerequisites and setup + +Setup happens at three levels: your organization, each service, and your individual account. + +### Enable Bits in your organization + +Bits Investigation requires Bits to be enabled and AI providers to be allowed for your organization. + +- If Bits is not enabled, turn it on from the Bits settings page. The settings page has two options: enabling Bits and enabling AI code fixes. +- If AI providers are blocked, Datadog AI features are unavailable for your organization. Contact your account admin or Datadog support to enable them. + +### Connect your source code + +Source Code Integration lets Bits Investigation read the code that was running when the error occurred. This improves accuracy and is required for suspect commits and code fixes. Connect a supported Git provider (GitHub or GitLab) and make sure your telemetry carries Git metadata. + +The setup depends on the platform: + +| Platform | What to configure | +|-----------------|----------------------------------------------------------------| +| Backend service | Set Git information in your deployment configuration. | +| Browser / RUM | Upload source maps with Git metadata. | +| Mobile | Upload debug symbols with Git metadata. | + +For the full steps, see [Source Code Integration][3]. + +### Connect your GitHub account + +Creating a pull request from a code fix requires connecting your individual GitHub account. You can run investigations and read results without it. + +## Run an investigation + +Investigations run on demand. + +1. Open an issue in Error Tracking. +2. In the issue side panel, click **Investigate**. +3. Wait for the investigation to finish. The result appears in the side panel. + +## Investigation results + +A result includes: + +- **Root cause**: the most likely reason the error occurs, with the evidence used to reach it. +- **Impact**: how many users, sessions, and accounts the issue affects. +- **Suspect commits**: the commits most likely to have introduced the error, when source code is connected. +- **Next step**: the recommended way to resolve the issue. + +If the investigation ran without source code, the result shows a reduced-context indicator and a link to set up Source Code Integration. + +## Resolve the issue + +From the result, you can: + +- **Fix with Bits Code**: when the issue is fixable through a code change, hand off to [Bits Code][1] to generate a fix and open a pull request. This option appears when Bits Investigation determines the issue is fixable in code. +- **Copy as Markdown**: copy the issue context for your AI assistant, then paste it into the agent of your choice. +- **Create a ticket**: open a ticket in [Jira, Linear, or Case Management][4]. +- **Resolve or ignore**: change the [issue state][5] directly from the panel. + +## Find issues with investigations + +Use the **with investigation** filter in the Error Tracking Explorer to find issues that already have a result. Issues with an investigation show an icon on their Explorer card. + +## Availability + +Bits Investigation in Error Tracking is in trial. While the trial is active, the product shows a trial badge. + +## Permissions + +Access to Bits Investigation follows your Bits AI permissions. Reading investigations and triggering them are controlled by your read and write access. + +Creating a pull request from a code fix also requires connecting your individual GitHub account, as described in [Connect your GitHub account](#connect-your-github-account). + +## Limitations + +- iOS error investigations are currently limited to error patterns and telemetry, because stack symbolication is not yet available. +- Bits Investigation works within a single repository. It does not investigate across multiple repositories. +- Bits Investigation uses AI and can make mistakes. Review and test any generated code before you merge it. + +## Further reading + +{{< partial name="whats-next/whats-next.html" >}} + +[1]: /bits_ai/bits_ai_dev_agent/ +[2]: /bits_ai/bits_ai_sre/ +[3]: /integrations/guide/source-code-integration/ +[4]: /error_tracking/ticketing_systems/ +[5]: /error_tracking/issue_states/ From 94ea6ea6b61e5ec9ca8ec4a8c1da35f393895b92 Mon Sep 17 00:00:00 2001 From: ThibaultK Date: Thu, 11 Jun 2026 15:52:44 +0200 Subject: [PATCH 2/4] Remove iOS limitation from Bits Investigation page --- content/en/error_tracking/bits_investigation.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/en/error_tracking/bits_investigation.md b/content/en/error_tracking/bits_investigation.md index 3fbd0c969e5..6a12cc0fb44 100644 --- a/content/en/error_tracking/bits_investigation.md +++ b/content/en/error_tracking/bits_investigation.md @@ -115,7 +115,6 @@ Creating a pull request from a code fix also requires connecting your individual ## Limitations -- iOS error investigations are currently limited to error patterns and telemetry, because stack symbolication is not yet available. - Bits Investigation works within a single repository. It does not investigate across multiple repositories. - Bits Investigation uses AI and can make mistakes. Review and test any generated code before you merge it. From 08c4519199c55427b240ca1c823831a3e43bb727 Mon Sep 17 00:00:00 2001 From: ThibaultK Date: Thu, 11 Jun 2026 16:22:50 +0200 Subject: [PATCH 3/4] Address review comments on Bits Investigation page Use established 'issue panel' term, emphasize Source Code Integration's effect on accuracy, trim literal step lists into How it works, simplify enablement, link the source map guide, note manual fix trigger and investigation re-run, and fold the Git account requirement (GitHub or GitLab) into Permissions. --- .../en/error_tracking/bits_investigation.md | 66 +++++++------------ 1 file changed, 22 insertions(+), 44 deletions(-) diff --git a/content/en/error_tracking/bits_investigation.md b/content/en/error_tracking/bits_investigation.md index 6a12cc0fb44..4696b54930f 100644 --- a/content/en/error_tracking/bits_investigation.md +++ b/content/en/error_tracking/bits_investigation.md @@ -19,7 +19,7 @@ further_reading: text: 'Bits Investigation for alerts and monitors (on-call)' --- -
Bits Investigation in Error Tracking is in trial. Behavior and availability can change, and the product shows a trial badge while the trial is active.
+
Bits Investigation in Error Tracking is in trial. Behavior and availability can change.
## Overview @@ -27,91 +27,68 @@ Bits Investigation is built into Error Tracking. When you open an issue, it inve This page covers Bits Investigation in Error Tracking. To investigate alerts and monitors during on-call, see [Bits Investigation for on-call operations][2]. - + ## How it works -You start an investigation from the issue side panel. Bits Investigation then: +You run an investigation on demand from the issue panel. Bits Investigation then: 1. Reads the issue, including the stack trace, error attributes, and related telemetry (logs, traces, and RUM events). 2. Reads the relevant source code when [Source Code Integration](#connect-your-source-code) is set up. 3. Forms a hypothesis about the root cause and checks it against the available data. -4. Returns a result: the root cause, an impact assessment, suspect commits, and a recommended next step. +4. Returns a result: the likely root cause with its supporting evidence, an impact assessment (how many users, sessions, and accounts are affected), suspect commits when source code is connected, and a recommended next step. From the result, you decide what to do next: generate a code fix with Bits Code, copy the context into your own AI assistant, create a ticket, or resolve or ignore the issue. -When source code is not connected, the investigation still runs but works from error patterns and telemetry only, so the result has less detail. The side panel marks these results so you know the investigation ran with reduced context. +
Connecting your source code has the largest effect on result quality. With Source Code Integration set up, Bits Investigation reads the code that was running when the error occurred, which sharpens root cause analysis and makes suspect commits and code fixes possible. Without it, investigations still run, but they work from error patterns and telemetry alone and the results are less precise.
## Prerequisites and setup -Setup happens at three levels: your organization, each service, and your individual account. - ### Enable Bits in your organization Bits Investigation requires Bits to be enabled and AI providers to be allowed for your organization. -- If Bits is not enabled, turn it on from the Bits settings page. The settings page has two options: enabling Bits and enabling AI code fixes. +- If Bits is not enabled, enable it from the Bits settings page. - If AI providers are blocked, Datadog AI features are unavailable for your organization. Contact your account admin or Datadog support to enable them. ### Connect your source code -Source Code Integration lets Bits Investigation read the code that was running when the error occurred. This improves accuracy and is required for suspect commits and code fixes. Connect a supported Git provider (GitHub or GitLab) and make sure your telemetry carries Git metadata. - -The setup depends on the platform: - -| Platform | What to configure | -|-----------------|----------------------------------------------------------------| -| Backend service | Set Git information in your deployment configuration. | -| Browser / RUM | Upload source maps with Git metadata. | -| Mobile | Upload debug symbols with Git metadata. | - -For the full steps, see [Source Code Integration][3]. - -### Connect your GitHub account - -Creating a pull request from a code fix requires connecting your individual GitHub account. You can run investigations and read results without it. +Source Code Integration lets Bits Investigation read the code that was running when the error occurred. It is required for suspect commits and code fixes, and it improves accuracy. Connect a supported Git provider (GitHub or GitLab) and make sure your telemetry carries Git information. -## Run an investigation +How you send Git information depends on the platform: -Investigations run on demand. +| Platform | What to configure | +|-----------------|---------------------------------------------------------| +| Backend service | Set Git information in your deployment configuration. | +| Browser / RUM | [Upload source maps][6] with Git information. | +| Mobile | Upload debug symbols with Git information. | -1. Open an issue in Error Tracking. -2. In the issue side panel, click **Investigate**. -3. Wait for the investigation to finish. The result appears in the side panel. - -## Investigation results - -A result includes: - -- **Root cause**: the most likely reason the error occurs, with the evidence used to reach it. -- **Impact**: how many users, sessions, and accounts the issue affects. -- **Suspect commits**: the commits most likely to have introduced the error, when source code is connected. -- **Next step**: the recommended way to resolve the issue. - -If the investigation ran without source code, the result shows a reduced-context indicator and a link to set up Source Code Integration. +For setup steps, see [Source Code Integration][3]. ## Resolve the issue -From the result, you can: +From a result, you can: -- **Fix with Bits Code**: when the issue is fixable through a code change, hand off to [Bits Code][1] to generate a fix and open a pull request. This option appears when Bits Investigation determines the issue is fixable in code. +- **Fix with Bits Code**: when the issue is fixable through a code change, hand off to [Bits Code][1] to generate a fix and open a pull request. This option appears when Bits Investigation determines the issue is fixable in code, and you can also trigger a fix manually when it does not. - **Copy as Markdown**: copy the issue context for your AI assistant, then paste it into the agent of your choice. - **Create a ticket**: open a ticket in [Jira, Linear, or Case Management][4]. - **Resolve or ignore**: change the [issue state][5] directly from the panel. +You can re-run an investigation at any time, and add your own context to guide it. + ## Find issues with investigations Use the **with investigation** filter in the Error Tracking Explorer to find issues that already have a result. Issues with an investigation show an icon on their Explorer card. ## Availability -Bits Investigation in Error Tracking is in trial. While the trial is active, the product shows a trial badge. +Bits Investigation in Error Tracking is in trial. ## Permissions -Access to Bits Investigation follows your Bits AI permissions. Reading investigations and triggering them are controlled by your read and write access. +Access to Bits Investigation follows your Bits AI permissions: reading and triggering investigations are controlled by your read and write access. -Creating a pull request from a code fix also requires connecting your individual GitHub account, as described in [Connect your GitHub account](#connect-your-github-account). +Running investigations and reading results does not require a personal Git connection. Creating a pull request from a code fix does: connect your individual GitHub or GitLab account first. ## Limitations @@ -127,3 +104,4 @@ Creating a pull request from a code fix also requires connecting your individual [3]: /integrations/guide/source-code-integration/ [4]: /error_tracking/ticketing_systems/ [5]: /error_tracking/issue_states/ +[6]: /real_user_monitoring/guide/upload-javascript-source-maps From 6c4bd05ad468ea9853b99d2786f7913a59b7110e Mon Sep 17 00:00:00 2001 From: ThibaultK Date: Thu, 11 Jun 2026 17:11:11 +0200 Subject: [PATCH 4/4] Fix Vale notices and address review comments Oxford comma in the overview, split two sentences over 25 words, link the mobile debug symbols docs, and add a screenshot TODO for re-running with added context. --- content/en/error_tracking/bits_investigation.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/content/en/error_tracking/bits_investigation.md b/content/en/error_tracking/bits_investigation.md index 4696b54930f..3248c33c9cb 100644 --- a/content/en/error_tracking/bits_investigation.md +++ b/content/en/error_tracking/bits_investigation.md @@ -23,7 +23,7 @@ further_reading: ## Overview -Bits Investigation is built into Error Tracking. When you open an issue, it investigates the error and reports the likely root cause, who and what is affected, and the recommended next step. When the resolution is a code change, it hands off to [Bits Code][1] to generate the fix. +Bits Investigation is built into Error Tracking. When you open an issue, it investigates the error and reports the likely root cause, the impact, and the recommended next step. When the resolution is a code change, it hands off to [Bits Code][1] to generate the fix. This page covers Bits Investigation in Error Tracking. To investigate alerts and monitors during on-call, see [Bits Investigation for on-call operations][2]. @@ -38,9 +38,9 @@ You run an investigation on demand from the issue panel. Bits Investigation then 3. Forms a hypothesis about the root cause and checks it against the available data. 4. Returns a result: the likely root cause with its supporting evidence, an impact assessment (how many users, sessions, and accounts are affected), suspect commits when source code is connected, and a recommended next step. -From the result, you decide what to do next: generate a code fix with Bits Code, copy the context into your own AI assistant, create a ticket, or resolve or ignore the issue. +From the result, you decide what to do next, as described in [Resolve the issue](#resolve-the-issue). -
Connecting your source code has the largest effect on result quality. With Source Code Integration set up, Bits Investigation reads the code that was running when the error occurred, which sharpens root cause analysis and makes suspect commits and code fixes possible. Without it, investigations still run, but they work from error patterns and telemetry alone and the results are less precise.
+
Connecting your source code has the largest effect on result quality. With Source Code Integration set up, Bits Investigation reads the code that was running when the error occurred. This sharpens root cause analysis and makes suspect commits and code fixes possible. Without it, investigations still run on error patterns and telemetry alone, so the results are less precise.
## Prerequisites and setup @@ -60,8 +60,8 @@ How you send Git information depends on the platform: | Platform | What to configure | |-----------------|---------------------------------------------------------| | Backend service | Set Git information in your deployment configuration. | -| Browser / RUM | [Upload source maps][6] with Git information. | -| Mobile | Upload debug symbols with Git information. | +| Browser | [Upload source maps][6] with Git information. | +| Mobile | [Upload debug symbols][7] with Git information. | For setup steps, see [Source Code Integration][3]. @@ -76,9 +76,11 @@ From a result, you can: You can re-run an investigation at any time, and add your own context to guide it. + + ## Find issues with investigations -Use the **with investigation** filter in the Error Tracking Explorer to find issues that already have a result. Issues with an investigation show an icon on their Explorer card. +Use the **Investigation Ready** filter in the Error Tracking Explorer to find issues that already have a result. Issues with an investigation show an icon on their Explorer card. ## Availability @@ -105,3 +107,4 @@ Running investigations and reading results does not require a personal Git conne [4]: /error_tracking/ticketing_systems/ [5]: /error_tracking/issue_states/ [6]: /real_user_monitoring/guide/upload-javascript-source-maps +[7]: /error_tracking/frontend/mobile/