You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Minor updates
- Removed preview sign up
- Updated Help Bits Learn screenshot
* Moved the preview info box
* Apply suggestions from code review
Co-authored-by: Esther Kim <esther.kim@datadoghq.com>
* Spacing update
---------
Co-authored-by: Esther Kim <esther.kim@datadoghq.com>
A subset of third-party integrations is in Preview. Click <strong>Request Access</strong> to join the Preview program.
21
-
{{< /callout >}}
22
-
23
19
## Send investigation findings to ITSM and collaboration platforms
24
20
25
21
By default, all investigations are listed on the [Bits AI Investigations][1] page.
@@ -32,13 +28,16 @@ For monitor alert investigations, a summary of the findings is available on the
32
28
1. Ensure the [Datadog Slack app][3] is installed in your Slack workspace.
33
29
1. In your monitor, go to **Configure notifications and automations** and add the `@slack-{channel-name}` handle. This sends monitor notifications to your chosen Slack channel.
34
30
1. Lastly, go to [**Bits AI SRE** > **Settings** > **Integrations**][4] and connect your Slack workspace. This allows Bits to write its findings directly under the monitor notification in Slack.
35
-
<divclass="alert alert-info">Each Slack workspace can only be connected to one Datadog organization.</div>
36
31
37
-
<!-- Commenting out this feature which was delayed
38
-
### Microsoft Teams
32
+
<divclass="alert alert-info">Each Slack workspace can only be connected to one Datadog organization.</div>
33
+
34
+
### Microsoft Teams (Preview)
35
+
39
36
1.[Connect your Microsoft tenant to Datadog][12].
40
37
1. In your monitor, go to **Configure notifications and automations** and add the `@teams-{handle-name}` handle. This sends monitor notifications to your chosen MS Teams channel. Bits will append its findings to these notifications.
41
-
-->
38
+
39
+
<divclass="alert alert-info">
40
+
The Microsoft Teams integration with Bits AI SRE is in Preview for all customers.</div>
Bits AI SRE investigations started from APM latency graphs and APM Watchdog stories are in Preview. Click <strong>Request Access</strong> to join the Preview program.
@@ -53,11 +53,7 @@ Bits AI SRE investigations started from APM latency graphs and APM Watchdog stor
53
53
54
54
On a Watchdog APM latency story, click **Investigate with Bits AI SRE**.
Starting Bits AI SRE investigations from chat prompts is in Preview. Click <strong>Request Access</strong> to join the Preview program.
60
-
{{< /callout >}}
56
+
#### General prompt (Preview)
61
57
62
58
Click on [New Investigation][16] and describe the issue you want to troubleshoot. Include as much relevant context as possible:
63
59
- Observed symptoms (e.g., errors, latency) including any links to Datadog telemetry that indicate this
@@ -75,6 +71,9 @@ Bad example:
75
71
76
72
You can also trigger an investigation from Slack. Mention Datadog in a message: `@Datadog Investigate high CPU in ai-gateway in prod over the last 30 minutes`. If invoked within a Slack thread, Bits AI SRE automatically uses the entire thread as investigation context.
77
73
74
+
<divclass="alert alert-info">
75
+
Starting Bits AI SRE investigations from a prompt is in Preview for all customers. During this period, the number of investigations per day is rate-limited. This limit does not apply to generally available entry points, such as monitors.</div>
76
+
78
77
### Enable automatic investigations
79
78
80
79
In addition to manual investigations, you can configure Bits to run automatically when a monitor transitions to the alert state:
@@ -102,9 +101,8 @@ Bits is able to run investigations on the following monitor types:
102
101
- APM (`APM Metrics` type only; `Trace Analytics` is not supported)
Starting Bits AI SRE investigations from Synthetic tests is now in Preview. Click <strong>Request Access</strong> to join the Preview program.
107
-
{{< /callout >}}
104
+
<divclass="alert alert-info">
105
+
Starting Bits AI SRE investigations from Synthetic tests is in Preview for all customers.</div>
108
106
109
107
## How Bits AI SRE investigates
110
108
When Bits AI SRE investigates an issue, it operates in a continuous loop of observation, reasoning, and action. It begins by forming hypotheses about the potential root cause, then uses its tools to query telemetry data to validate or invalidate those hypotheses. Each step builds on prior findings. As new evidence emerges, Bits AI SRE updates its understanding, refines its reasoning, and chains together additional investigative steps—adapting and course-correcting until it converges on the most likely root cause.
@@ -140,9 +138,8 @@ Bits uses the following data sources during investigations:
<b>Bits.md</b> is in Preview. Click <strong>Request Access</strong> to join the Preview program.
32
-
{{< /callout >}}
30
+
<divclass="alert alert-info">
31
+
Bits.md is in Preview for all customers.</div>
33
32
34
33
You can proactively guide how Bits investigates your environment by creating a `bits.md` file at [**Bits AI SRE** > **Settings** > **Bits.md**][2].
35
34
@@ -104,7 +103,7 @@ Rule:
104
103
105
104
At the end of an investigation, let Bits AI SRE know whether the conclusion it made was correct.
106
105
107
-
{{< img src="bits_ai/help_bits_ai_learn_1.png" alt="An investigation conclusion with the helpful and unhelpful rating buttons highlighted" style="width:100%;" >}}
106
+
{{< img src="bits_ai/help_bits_ai_learn_2.png" alt="Post-investigation root cause feedback flow" style="width:100%;" >}}
108
107
109
108
If the conclusion was inaccurate, provide Bits AI SRE with the correct root cause, highlighting what it missed, and explaining what it should do differently next time. Your feedback should:
110
109
- Identify the actual root cause (not just observed effects or symptoms)
0 commit comments