Skip to content

Commit daf995f

Browse files
kaixintaiestherk15
andauthored
Minor updates to Bits AI SRE docs (#35767)
* 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>
1 parent 5c8b223 commit daf995f

4 files changed

Lines changed: 19 additions & 24 deletions

File tree

content/en/bits_ai/bits_ai_sre/configure.md

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -16,10 +16,6 @@ To configure GitHub:
1616
1. Install the [GitHub integration][13].
1717
1. [Tag your APM telemetry with Git information][14] to link running application versions to specific repositories and commits.
1818

19-
{{< callout url="http://datadoghq.com/product-preview/bits-ai-sre-pilot-features" >}}
20-
A subset of third-party integrations is in Preview. Click <strong>Request Access</strong> to join the Preview program.
21-
{{< /callout >}}
22-
2319
## Send investigation findings to ITSM and collaboration platforms
2420

2521
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
3228
1. Ensure the [Datadog Slack app][3] is installed in your Slack workspace.
3329
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.
3430
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-
<div class="alert alert-info">Each Slack workspace can only be connected to one Datadog organization.</div>
3631

37-
<!-- Commenting out this feature which was delayed
38-
### Microsoft Teams
32+
<div class="alert alert-info">Each Slack workspace can only be connected to one Datadog organization.</div>
33+
34+
### Microsoft Teams (Preview)
35+
3936
1. [Connect your Microsoft tenant to Datadog][12].
4037
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+
<div class="alert alert-info">
40+
The Microsoft Teams integration with Bits AI SRE is in Preview for all customers.</div>
4241

4342
### Datadog Case Management
4443

content/en/bits_ai/bits_ai_sre/investigate_issues.md

Lines changed: 9 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ To use the Slack integration, [connect your Slack workspace to Bits AI SRE][8].
3737

3838
In Slack, reply to a monitor notification with `@Datadog Investigate this alert`.
3939

40-
#### APM latency
40+
#### APM latency (Preview)
4141

4242
{{< callout url="http://datadoghq.com/product-preview/bits-ai-sre-pilot-features" >}}
4343
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
5353

5454
On a Watchdog APM latency story, click **Investigate with Bits AI SRE**.
5555

56-
#### General prompt
57-
58-
{{< callout url="http://datadoghq.com/product-preview/bits-ai-sre-pilot-features" >}}
59-
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)
6157

6258
Click on [New Investigation][16] and describe the issue you want to troubleshoot. Include as much relevant context as possible:
6359
- Observed symptoms (e.g., errors, latency) including any links to Datadog telemetry that indicate this
@@ -75,6 +71,9 @@ Bad example:
7571

7672
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.
7773

74+
<div class="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+
7877
### Enable automatic investigations
7978

8079
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:
102101
- APM (`APM Metrics` type only; `Trace Analytics` is not supported)
103102
- Synthetics API and Browser tests (Preview)
104103

105-
{{< callout url="http://datadoghq.com/product-preview/bits-ai-sre-pilot-features" >}}
106-
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+
<div class="alert alert-info">
105+
Starting Bits AI SRE investigations from Synthetic tests is in Preview for all customers.</div>
108106

109107
## How Bits AI SRE investigates
110108
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:
140138
- ServiceNow
141139
- Confluence
142140

143-
{{< callout url="http://datadoghq.com/product-preview/bits-ai-sre-pilot-features" >}}
144-
A subset of third-party integrations are in Preview. Click <strong>Request Access</strong> to join the Preview program.
145-
{{< /callout >}}
141+
<div class="alert alert-info">
142+
Third-party integrations are in Preview for all customers.</div>
146143

147144
For best practices on maximizing the effectiveness of investigations, see [Knowledge sources][9].
148145

content/en/bits_ai/bits_ai_sre/knowledge_sources.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -27,9 +27,8 @@ To maximize the value of this integration, document the services, dependencies,
2727

2828
## Bits.md
2929

30-
{{< callout url="https://datadoghq.com/product-preview/bits-ai-sre-pilot-features" >}}
31-
<b>Bits.md</b> is in Preview. Click <strong>Request Access</strong> to join the Preview program.
32-
{{< /callout >}}
30+
<div class="alert alert-info">
31+
Bits.md is in Preview for all customers.</div>
3332

3433
You can proactively guide how Bits investigates your environment by creating a `bits.md` file at [**Bits AI SRE** > **Settings** > **Bits.md**][2].
3534

@@ -104,7 +103,7 @@ Rule:
104103

105104
At the end of an investigation, let Bits AI SRE know whether the conclusion it made was correct.
106105

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%;" >}}
108107

109108
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:
110109
- Identify the actual root cause (not just observed effects or symptoms)
391 KB
Loading

0 commit comments

Comments
 (0)