?` | APM |
-| Ask about Datadog products | `Does Bits AI SRE connect to Datadog Case Management?` | Datadog Documentation |
+| Ask about Datadog products | `Does Bits Investigation connect to Datadog Case Management?` | Datadog Documentation |
| Create a Notebook | `Can you create a notebook with a summary of this investigation?` | Notebooks |
[1]: bits_ai/bits_ai_sre/configure#confluence
diff --git a/content/en/bits_ai/bits_ai_sre/configure.md b/content/en/bits_ai/bits_ai_sre/configure.md
index dcaab2a7633..8101355c596 100644
--- a/content/en/bits_ai/bits_ai_sre/configure.md
+++ b/content/en/bits_ai/bits_ai_sre/configure.md
@@ -2,14 +2,14 @@
title: Configure Integrations and Settings
---
-Set up integrations to extend Bits AI SRE’s capabilities:
+Set up integrations to extend Bits Investigation’s capabilities:
- [Integrate with third-party observability and SCM platforms](#integrate-with-third-party-observability-and-scm-platforms) to enrich investigations with external telemetry and code context.
- [Send investigation findings to ITSM and collaboration platforms](#send-investigation-findings-to-itsm-and-collaboration-platforms) to streamline incident response.
- [Pull context from knowledge bases](#pull-context-from-knowledge-bases) to incorporate runbooks and documentation into investigations.
## Integrate with third-party observability and SCM platforms
-Bits AI SRE integrates with GitHub, Grafana, Dynatrace, Splunk, Sentry, and ServiceNow to incorporate observability data and source code into investigations. Source code access is also required for the Bits Dev Agent to generate a code fix when Bits AI SRE identifies an issue that can be resolved in code.
+Bits Investigation integrates with GitHub, Grafana, Dynatrace, Splunk, Sentry, and ServiceNow to incorporate observability data and source code into investigations. Source code access is also required for Bits Code to generate a code fix when Bits Investigation identifies an issue that can be resolved in code.
### GitHub
To configure GitHub:
@@ -27,7 +27,7 @@ For monitor alert investigations, a summary of the findings is available on the
1. Ensure the [Datadog Slack app][3] is installed in your Slack workspace.
1. In your monitor, go to {{< ui >}}Configure notifications and automations{{< /ui >}} and add the `@slack-{channel-name}` handle. This sends monitor notifications to your chosen Slack channel.
-1. Lastly, go to [{{< ui >}}Bits AI SRE{{< /ui >}} > {{< ui >}}Settings{{< /ui >}} > {{< ui >}}Integrations{{< /ui >}}][4] and connect your Slack workspace. This allows Bits to write its findings directly under the monitor notification in Slack.
+1. Lastly, go to [{{< ui >}}Bits Investigation{{< /ui >}} > {{< ui >}}Settings{{< /ui >}} > {{< ui >}}Integrations{{< /ui >}}][4] and connect your Slack workspace. This allows Bits to write its findings directly under the monitor notification in Slack.
Each Slack workspace can only be connected to one Datadog organization.
@@ -37,11 +37,11 @@ For monitor alert investigations, a summary of the findings is available on the
1. In your monitor, go to {{< ui >}}Configure notifications and automations{{< /ui >}} 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.
-The Microsoft Teams integration with Bits AI SRE is in Preview for all customers.
+The Microsoft Teams integration with Bits Investigation is in Preview for all customers.
### Datadog Case Management
-Datadog Case Management provides a centralized workspace for triaging, tracking, and remediating issues detected by Datadog and third-party integrations. Bits AI SRE automatically delivers its investigation findings to Jira and ServiceNow through Case Management.
+Datadog Case Management provides a centralized workspace for triaging, tracking, and remediating issues detected by Datadog and third-party integrations. Bits Investigation automatically delivers its investigation findings to Jira and ServiceNow through Case Management.
To set up Case Management, and the Jira and ServiceNow integrations:
1. Create a [Case Management project][5] for your team.
@@ -61,11 +61,11 @@ To set up On-Call, in your monitor, go to {{< ui >}}Configure notifications and
## Pull context from knowledge bases
### Confluence
-Bits AI SRE integrates with Confluence to:
+Bits Investigation integrates with Confluence to:
- Find relevant documentation and runbooks to support its monitor alert investigations
- Let you interact with your Confluence content directly through chat
-To set up Bits AI SRE to use Confluence:
+To set up Bits Investigation to use Confluence:
1. Connect your Confluence Cloud account by following the instructions in the [Confluence integration tile][7].
1. Optionally, enable account crawling to make Confluence a data source within Bits' chat interface. If you don't enable account crawling, Bits can still use Confluence to inform its investigation plan.
@@ -74,7 +74,7 @@ To set up Bits AI SRE to use Confluence:
## Configure permissions
-There are two RBAC permissions that apply to Bits AI SRE:
+There are two RBAC permissions that apply to Bits Investigation:
| Name | Description | Default role |
|:--------------------------------------------------------|:---------------------------------------|:-----------------------|
@@ -85,7 +85,7 @@ These permissions are added by default to Managed Roles. If your organization us
## Configure rate limits
-Rate limits define the maximum number of automatic investigations Bits AI SRE can run in a rolling 24-hour period. After you reach a rate limit, you can continue to trigger [manual investigations][9].
+Rate limits define the maximum number of automatic investigations Bits Investigation can run in a rolling 24-hour period. After you reach a rate limit, you can continue to trigger [manual investigations][9].
### Types of rate limits
@@ -95,13 +95,13 @@ Per monitor limit
: **Default:** Each monitor can trigger one automatic investigation per 24 hours.
Organization limit
-: Defines the total number of automatic investigations Bits AI SRE can run across your entire organization within 24 hours.
+: Defines the total number of automatic investigations Bits Investigation can run across your entire organization within 24 hours.
: **Default:** No limit.
### Set a rate limit
To set a rate limit:
-1. Navigate to [{{< ui >}}Bits AI SRE{{< /ui >}} > {{< ui >}}Settings{{< /ui >}} > {{< ui >}}Rate Limits{{< /ui >}}][10].
+1. Navigate to [{{< ui >}}Bits Investigation{{< /ui >}} > {{< ui >}}Settings{{< /ui >}} > {{< ui >}}Rate Limits{{< /ui >}}][10].
2. Toggle on the rate limit you want to enable.
3. Set the maximum number of investigations you want to run within a rolling 24-hour window.
4. Click {{< ui >}}Save{{< /ui >}}.
@@ -118,7 +118,7 @@ You can monitor user-initiated actions with [Audit Trail][11]. Events are sent w
## Actions
-Bits AI SRE provides three [Actions][15]:
+Bits Investigation provides three [Actions][15]:
- Trigger Investigation
- Get Investigation
- List Investigations
diff --git a/content/en/bits_ai/bits_ai_sre/investigate_issues.md b/content/en/bits_ai/bits_ai_sre/investigate_issues.md
index 418322a5d66..603c5e98d29 100644
--- a/content/en/bits_ai/bits_ai_sre/investigate_issues.md
+++ b/content/en/bits_ai/bits_ai_sre/investigate_issues.md
@@ -1,17 +1,17 @@
---
title: Investigate Issues
-description: "Use Bits AI SRE to automatically investigate monitor alerts and provide root cause analysis for faster incident resolution."
+description: "Use Bits Investigation to automatically investigate monitor alerts and provide root cause analysis for faster incident resolution."
aliases:
- /bits_ai/bits_ai_sre/investigate_alerts/
further_reading:
- link: "https://www.datadoghq.com/blog/bits-ai-sre-deeper-reasoning"
tag: "Blog"
- text: "Meet the new Bits AI SRE: Deeper reasoning, twice as fast"
+ text: "Meet the new Bits Investigation: Deeper reasoning, twice as fast"
---
-## Start a Bits AI SRE investigation
+## Start a Bits Investigation
-You can launch a Bits AI SRE investigation from several entry points:
+You can launch a Bits Investigation from several entry points:
- Monitor alerts, which you can trigger in two ways:
- [**Manual**](#manual-monitor-alerts): Start from an individual monitor alert
@@ -25,49 +25,49 @@ You can launch a Bits AI SRE investigation from several entry points:
You can invoke Bits on an individual monitor alert or warn event from several entry points:
-#### Option 1: Bits AI SRE Monitors list {#monitor-list}
-1. Go to [{{< ui >}}Bits AI SRE{{< /ui >}} > {{< ui >}}Monitors{{< /ui >}} > {{< ui >}}Supported{{< /ui >}}][5].
+#### Option 1: Bits Investigation Monitors list {#monitor-list}
+1. Go to [{{< ui >}}Bits Investigation{{< /ui >}} > {{< ui >}}Monitors{{< /ui >}} > {{< ui >}}Supported{{< /ui >}}][5].
1. Click {{< ui >}}Investigate Recent Alerts{{< /ui >}} and select an alert.
#### Option 2: Monitor status page
-Navigate to the monitor status page of a [Bits AI SRE-supported monitor](#supported-monitors) and click {{< ui >}}Investigate with Bits AI SRE{{< /ui >}} in the top-right corner.
+Navigate to the monitor status page of a [Bits Investigation-supported monitor](#supported-monitors) and click {{< ui >}}Investigate with Bits Investigation{{< /ui >}} in the top-right corner.
#### Option 3: Monitor event side panel
-In the monitor event side panel of a [Bits AI SRE-supported monitor](#supported-monitors), click {{< ui >}}Investigate with Bits AI SRE{{< /ui >}}.
+In the monitor event side panel of a [Bits Investigation-supported monitor](#supported-monitors), click {{< ui >}}Investigate with Bits Investigation{{< /ui >}}.
#### Option 4: Slack
-To use the Slack integration, [connect your Slack workspace to Bits AI SRE][8].
+To use the Slack integration, [connect your Slack workspace to Bits Investigation][8].
In Slack, reply to a monitor notification with `@Datadog Investigate this alert`.
### APM latency (Preview)
{{< callout url="http://datadoghq.com/product-preview/bits-ai-sre-pilot-features" >}}
-Bits AI SRE investigations started from APM latency graphs and APM Watchdog stories are in Preview. Click Request Access to join the Preview program.
+Bits Investigations started from APM latency graphs and APM Watchdog stories are in Preview. Click Request Access to join the Preview program.
{{< /callout >}}
#### APM latency graphs on service pages
1. In Datadog, navigate to [APM][1] and open the service or resource page you want to investigate. Next to the latency graph, click {{< ui >}}Investigate{{< /ui >}}.
1. Click and drag your cursor over the point plot visualization to make a rectangular selection over a region that shows unusual latency to seed the analysis. Initial diagnostics on the latency issue appear, including the observed user impact, anomalous tags contributing to the issue, and recent changes. For more information, see [APM Investigator][2].
-1. Click {{< ui >}}Investigate with Bits AI SRE{{< /ui >}} to run a deeper investigation.
+1. Click {{< ui >}}Investigate with Bits Investigation{{< /ui >}} to run a deeper investigation.
#### APM latency Watchdog stories
-On a Watchdog APM latency story, click {{< ui >}}Investigate with Bits AI SRE{{< /ui >}}.
+On a Watchdog APM latency story, click {{< ui >}}Investigate with Bits Investigation{{< /ui >}}.
### Synthetic tests (Preview)
-Bits AI SRE investigations started from Synthetic Browser and API tests are in Preview.
+Bits Investigations started from Synthetic Browser and API tests are in Preview.
-When a Synthetic Browser or API test monitor triggers, you can launch a Bits AI SRE investigation to identify the root cause. Bits AI SRE analyzes Synthetic test results and history alongside traces, logs, and metrics. It surfaces a likely root cause and identifies whether the failure reflects a real regression or a misconfiguration.
+When a Synthetic Browser or API test monitor triggers, you can launch a Bits Investigation to identify the root cause. Bits Investigation analyzes Synthetic test results and history alongside traces, logs, and metrics. It surfaces a likely root cause and identifies whether the failure reflects a real regression or a misconfiguration.
#### From the Synthetic test details page
1. On the [Synthetic Tests][18] page, open the Synthetic test you want to investigate and go to the {{< ui >}}Timeline{{< /ui >}} section.
1. Select the {{< ui >}}Alert Triggered{{< /ui >}} event for the failing test run.
-1. Click {{< ui >}}Investigate with Bits AI SRE{{< /ui >}}.
+1. Click {{< ui >}}Investigate with Bits Investigation{{< /ui >}}.
The investigation opens in a new page, and you can also view it from the test details page after it runs.
@@ -91,22 +91,22 @@ Good examples:
Bad example:
- App is slow. What’s wrong?
-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.
+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 Investigation automatically uses the entire thread as investigation context.
-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.
+Starting Bits 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.
### Enable automatic investigations
In addition to manual investigations, you can configure Bits to run automatically when a monitor transitions to the alert state:
-#### From the Bits AI SRE Monitors list
-1. Go to [{{< ui >}}Bits AI SRE{{< /ui >}} > {{< ui >}}Monitors{{< /ui >}} > {{< ui >}}Supported{{< /ui >}}][5].
+#### From the Bits Investigation Monitors list
+1. Go to [{{< ui >}}Bits Investigation{{< /ui >}} > {{< ui >}}Monitors{{< /ui >}} > {{< ui >}}Supported{{< /ui >}}][5].
1. Toggle {{< ui >}}Auto-Investigate{{< /ui >}} on for a single monitor, or bulk-edit multiple monitors by selecting multiple monitors, then clicking {{< ui >}}Auto-Investigate All{{< /ui >}}.
#### For a single monitor
1. Open the monitor's status page and click {{< ui >}}Edit{{< /ui >}}.
-1. Scroll to {{< ui >}}Configure notifications & automations{{< /ui >}} and toggle {{< ui >}}Investigate with Bits AI SRE{{< /ui >}}.
+1. Scroll to {{< ui >}}Configure notifications & automations{{< /ui >}} and toggle {{< ui >}}Investigate with Bits Investigation{{< /ui >}}.
- Enabling automatic investigations using the Datadog API or Terraform is not supported.
- An investigation initiates when a monitor transitions to the alert state.
- Transitions to the warn or no data state, renotifications, and test notifications do not trigger automatic investigations.
Add service scoping: For monitors associated with a service, add a service tag to the monitor, or filter or group the monitor query by service. This helps Bits AI SRE correlate data more accurately.
+Add service scoping: For monitors associated with a service, add a service tag to the monitor, or filter or group the monitor query by service. This helps Bits Investigation correlate data more accurately.
#### Third-party integrations
- Grafana
@@ -174,7 +174,7 @@ Once the investigation is complete, you can switch to the {{< ui >}}Investigatio
## Reports
-The {{< ui >}}Reports{{< /ui >}} tab enables you to track the number of investigations run over time by monitor, user, service, and team. You can also track the mean time to conclusion to assess the impact of Bits AI SRE on your on-call efficiency.
+The {{< ui >}}Reports{{< /ui >}} tab enables you to track the number of investigations run over time by monitor, user, service, and team. You can also track the mean time to conclusion to assess the impact of Bits Investigation on your on-call efficiency.
[1]: https://app.datadoghq.com/apm/home
[2]: /tracing/guide/latency_investigator/
diff --git a/content/en/bits_ai/bits_ai_sre/knowledge_sources.md b/content/en/bits_ai/bits_ai_sre/knowledge_sources.md
index f5ea9b28200..c37e771b9f7 100644
--- a/content/en/bits_ai/bits_ai_sre/knowledge_sources.md
+++ b/content/en/bits_ai/bits_ai_sre/knowledge_sources.md
@@ -5,25 +5,25 @@ aliases:
---
-Bits AI SRE improves over time by combining three distinct sources of knowledge:
+Bits Investigation improves over time by combining three distinct sources of knowledge:
- [**Runbooks:**](#runbooks) Step-by-step troubleshooting guidance
- [**bits.md:**](#bitsmd) Context about your environment
- [**Feedback and memories:**](#feedback-and-memories) Learnings from investigations
## Runbooks
-Think of onboarding Bits AI SRE as you would a new teammate: the more context you provide, the better it can investigate.
+Think of onboarding Bits Investigation as you would a new teammate: the more context you provide, the better it can investigate.
You can either add step-by-step troubleshooting instructions directly in the monitor message or link to a Confluence page that contains those instructions.
- **Include Datadog telemetry links**: When adding instructions in the monitor message, include links to the most relevant telemetry. Start with the first place you'd normally look in Datadog when the monitor triggers, such as a dashboard, logs, traces, or a notebook with key widgets. Links don't need special formatting; plain URLs work.
-Because these links are user-defined, you have control over what Bits AI SRE reviews, ensuring it focuses on the same data you would, and giving you the flexibility to tailor investigations to your team's workflows.
+Because these links are user-defined, you have control over what Bits Investigation reviews, ensuring it focuses on the same data you would, and giving you the flexibility to tailor investigations to your team's workflows.
- **Notebooks**: Monitors can link to notebooks that contain instructions on how to troubleshoot the monitor or related service. Notebooks support markdown as well as Datadog queries, giving the agent instructions on how to best perform root cause analysis.
-- **Confluence integration**: If your runbooks live in Confluence, link the relevant pages in the monitor message. During an investigation, Bits AI SRE reads the page, extracts telemetry links, follows documented troubleshooting steps where possible, and incorporates remediation guidance into its recommendations.
+- **Confluence integration**: If your runbooks live in Confluence, link the relevant pages in the monitor message. During an investigation, Bits Investigation reads the page, extracts telemetry links, follows documented troubleshooting steps where possible, and incorporates remediation guidance into its recommendations.
-To maximize the value of this integration, document the services, dependencies, and systems involved in detail, and provide clear, step-by-step instructions for resolving the issue. Well-structured, specific runbooks enable Bits AI SRE to conduct more accurate and effective investigations.
+To maximize the value of this integration, document the services, dependencies, and systems involved in detail, and provide clear, step-by-step instructions for resolving the issue. Well-structured, specific runbooks enable Bits Investigation to conduct more accurate and effective investigations.
{{< img src="bits_ai/optimization_example.png" alt="Example monitor with optimization steps applied" style="width:100%;" >}}
@@ -32,7 +32,7 @@ To maximize the value of this integration, document the services, dependencies,
Bits.md is in Preview for all customers.
-You can proactively guide how Bits investigates your environment by creating a `bits.md` file at [{{< ui >}}Bits AI SRE{{< /ui >}} > {{< ui >}}Settings{{< /ui >}} > {{< ui >}}Bits.md{{< /ui >}}][2].
+You can proactively guide how Bits investigates your environment by creating a `bits.md` file at [{{< ui >}}Bits Investigation{{< /ui >}} > {{< ui >}}Settings{{< /ui >}} > {{< ui >}}Bits.md{{< /ui >}}][2].
`bits.md` is a Markdown file that provides structured context about your environment to Bits. It serves as lightweight guidance to improve investigation accuracy, query construction, and terminology alignment. Add team-specific knowledge such as tagging conventions, architectural patterns, glossary terms, and investigation best practices.
@@ -103,18 +103,18 @@ Rule:
## Feedback and memories
-At the end of an investigation, let Bits AI SRE know whether the conclusion it made was correct.
+At the end of an investigation, let Bits Investigation know whether the conclusion it made was correct.
{{< img src="bits_ai/help_bits_ai_learn_2.png" alt="Post-investigation root cause feedback flow" style="width:100%;" >}}
-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:
+If the conclusion was inaccurate, provide Bits Investigation with the correct root cause, highlighting what it missed, and explaining what it should do differently next time. Your feedback should:
- Identify the actual root cause (not just observed effects or symptoms)
- Specify relevant services, components, or metrics
- Include telemetry links that point to the root cause
**Example high-quality root cause feedback**: "High memory usage in auth-service pod due to memory leak in session cache, causing OOM kills every 2 hours starting at 2025-11-15 14:30 UTC. This is evidenced by `https://app.datadoghq.com/logs?`"
-All positive feedback, as well as any negative feedback that includes details provided in the Bits' chat, creates a **memory**. Bits AI SRE dynamically selects which memories to use in future investigations to improve its performance. It applies past corrections in similar contexts, reuses effective queries, and refines how it prioritizes investigative steps. Over time, this enables Bits AI SRE to adapt to your environment, becoming more accurate and efficient with each investigation.
+All positive feedback, as well as any negative feedback that includes details provided in the Bits' chat, creates a **memory**. Bits Investigation dynamically selects which memories to use in future investigations to improve its performance. It applies past corrections in similar contexts, reuses effective queries, and refines how it prioritizes investigative steps. Over time, this enables Bits Investigation to adapt to your environment, becoming more accurate and efficient with each investigation.
To manage memories, including viewing and deleting them, go to the {{< ui >}}Memories{{< /ui >}} column of the [Monitor Management][1] page.
diff --git a/content/en/bits_ai/bits_ai_sre/take_action.md b/content/en/bits_ai/bits_ai_sre/take_action.md
index 24795db026e..8030b568c37 100644
--- a/content/en/bits_ai/bits_ai_sre/take_action.md
+++ b/content/en/bits_ai/bits_ai_sre/take_action.md
@@ -4,16 +4,16 @@ aliases:
- /bits_ai/bits_ai_sre/remediate_issues/
---
-## Suggested code fixes from the Bits AI Dev Agent
+## Suggested code fixes from Bits Code
{{< callout url="http://datadoghq.com/product-preview/bits-ai-sre-pilot-features" >}}
-Suggested code fixes from the Bits AI Dev Agent is in Preview. Click Request Access to join the Preview program.
+Suggested code fixes from Bits Code is in Preview. Click Request Access to join the Preview program.
{{< /callout >}}
-After Bits AI SRE helps you identify a root cause, it can also help you take action as quickly as possible.
+After Bits Investigation helps you identify a root cause, it can also help you take action as quickly as possible.
-Bits AI SRE integrates with [Bits AI Dev Agent][2] to automatically generate code fixes. The Dev Agent connects to GitHub to create production-ready pull requests, iterates on fixes using CI logs and developer feedback, and uses multiple Datadog products to generate contextual fixes.
-1. [Set up the Bits AI Dev Agent][1]. Then, after Bits AI SRE has determined a code-related root cause, you will automatically receive suggested code fixes.
-1. Ask Bits AI Dev Agent to make any additional updates as needed, create a pull request for review in GitHub, and merge when ready to fix the underlying problem.
+Bits Investigation integrates with [Bits Code][2] to automatically generate code fixes. Bits Code connects to GitHub to create production-ready pull requests, iterates on fixes using CI logs and developer feedback, and uses multiple Datadog products to generate contextual fixes.
+1. [Set up Bits Code][1]. Then, after Bits Investigation has determined a code-related root cause, you will automatically receive suggested code fixes.
+1. Ask Bits Code to make any additional updates as needed, create a pull request for review in GitHub, and merge when ready to fix the underlying problem.
{{< img src="bits_ai/bits_ai_sre_suggested_code_fix.png" alt="Flowchart showing Bits' investigation conclusion and a suggested code fix" style="width:100%;" >}}
@@ -27,7 +27,7 @@ Supported actions include:
- Creating cases in Datadog Case Management
- Opening Jira tickets
-Bits AI SRE automatically pulls relevant context from the investigation and your connected integrations to prefill messages, incident descriptions, and ticket metadata. This reduces manual effort, ensures consistency, and accelerates response time.
+Bits Investigation automatically pulls relevant context from the investigation and your connected integrations to prefill messages, incident descriptions, and ticket metadata. This reduces manual effort, ensures consistency, and accelerates response time.
[1]: /bits_ai/bits_ai_dev_agent/setup/
[2]: /bits_ai/bits_ai_dev_agent
diff --git a/content/en/bits_ai/bits_assistant.md b/content/en/bits_ai/bits_assistant.md
index c3b04cf60f9..37d38fa2af6 100644
--- a/content/en/bits_ai/bits_assistant.md
+++ b/content/en/bits_ai/bits_assistant.md
@@ -1,6 +1,6 @@
---
-title: Bits AI Assistant
-description: "Use Bits AI Assistant in Datadog to explore and act on your observability data using natural language."
+title: Bits Chat
+description: "Use Bits Chat in Datadog to explore and act on your observability data using natural language."
further_reading:
- link: "bits_ai/"
tag: "Documentation"
@@ -10,16 +10,16 @@ further_reading:
text: "Coordinate incidents with Incident AI"
- link: "/cloud_cost_management/cloud_cost_skill/"
tag: "Documentation"
- text: "Cloud Cost Skill in Bits AI Assistant"
+ text: "Cloud Cost Skill in Bits Chat"
aliases:
- /bits_ai/getting_started/
- /bits_ai/chat_with_bits_ai
---
## Overview
-Bits AI Assistant is an AI-powered companion in Datadog that helps you search and act across Datadog using natural language. Bits AI Assistant is available across the web application, mobile app, and Slack.
+Bits Chat is an AI-powered companion in Datadog that helps you search and act across Datadog using natural language. Bits Chat is available across the web application, mobile app, and Slack.
-Ask Bits AI Assistant questions across these categories:
+Ask Bits Chat questions across these categories:
### Investigate issues and remediate
- `Summarize high severity incidents that have occurred in the last day`
@@ -47,22 +47,22 @@ Ask Bits AI Assistant questions across these categories:
- `How can I put a team tag on this monitor?`
- `Add a timeseries widget for request count over time to this notebook`
-{{< img src="bits_ai/getting_started/bits_assistant_full_page.png" alt="Full-page Bits AI Assistant interface showing conversation history and prompt suggestions" style="width:100%;">}}
+{{< img src="bits_ai/getting_started/bits_assistant_full_page.png" alt="Full-page Bits Chat interface showing conversation history and prompt suggestions" style="width:100%;">}}
### Permissions
-#### Access to Bits AI Assistant
+#### Access to Bits Chat
-To use Bits AI Assistant, your role must have the **Bits Assistant Access** permission. This permission is enabled by default for all three standard Datadog roles: Datadog Admin, Datadog Standard, and Datadog Read Only.
+To use Bits Chat, your role must have the **Bits Chat Access** permission. This permission is enabled by default for all three standard Datadog roles: Datadog Admin, Datadog Standard, and Datadog Read Only.
-To manage this permission for custom roles, go to **Organization Settings** > **Roles**, select a role, and toggle **Bits Assistant Access** under **General Permissions**.
+To manage this permission for custom roles, go to **Organization Settings** > **Roles**, select a role, and toggle **Bits Chat Access** under **General Permissions**.
-#### Data access through Bits AI Assistant
+#### Data access through Bits Chat
-Bits AI Assistant uses your Datadog role to fetch data, so it can only access the resources you have permission to view or modify. For example, if your role restricts access to a specific set of logs indexes, Bits AI Assistant can only query logs from those indexes. Similarly, if you do not have permission to edit a dashboard, Bits AI Assistant cannot edit that dashboard on your behalf.
+Bits Chat uses your Datadog role to fetch data, so it can only access the resources you have permission to view or modify. For example, if your role restricts access to a specific set of logs indexes, Bits Chat can only query logs from those indexes. Similarly, if you do not have permission to edit a dashboard, Bits Chat cannot edit that dashboard on your behalf.
### Skills
-Bits AI Assistant has a range of specialized skills for tasks across Datadog. The most commonly used skills are described below.
+Bits Chat has a range of specialized skills for tasks across Datadog. The most commonly used skills are described below.
#### Dashboards
Build [dashboards][5] and widgets from natural language descriptions.
@@ -95,7 +95,7 @@ Example prompts:
- `What's the latency bottleneck for this service?`
#### Cloud Cost Management
-Investigate [cloud cost][4] changes and identify the teams or resources responsible. See [Cloud Cost Skill in Bits AI Assistant][9].
+Investigate [cloud cost][4] changes and identify the teams or resources responsible. See [Cloud Cost Skill in Bits Chat][9].
Example prompts:
- `Investigate why EC2 costs changed between January and February`
@@ -111,31 +111,31 @@ Example prompts:
### Reports
-The Bits AI Assistant Reports page provides visibility into how your organization uses Bits AI Assistant. Go to [**Bits AI** > **Assistant** > **Reports**][10] to view:
+The Bits Chat Reports page provides visibility into how your organization uses Bits Chat. Go to [**Bits AI** > **Chat** > **Reports**][10] to view:
-- **Top users**: See which team members use Bits AI Assistant the most, ranked by conversation count.
+- **Top users**: See which team members use Bits Chat the most, ranked by conversation count.
- **Usage trends**: Track conversation volume over time to understand adoption and identify usage patterns.
- **Conversation intent distribution**: See how conversations break down by intent category, such as investigating issues, exploring telemetry, learning Datadog concepts, and configuring observability.
Use these insights to understand adoption patterns, identify power users for best-practice sharing, and assess which use cases deliver the most value for your organization.
### Web application
-There are multiple ways to open Bits AI Assistant in the Datadog web application:
+There are multiple ways to open Bits Chat in the Datadog web application:
- In the top-right of the navigation bar, click {{< ui >}}Ask Bits{{< /ui >}}
-- In a Datadog product integrated with Bits AI Assistant, click {{< ui >}}Ask Bits{{< /ui >}} or {{< img src="bits_ai/dev_agent/twinkling_stars_icon.png" inline="true" style="width:24px">}} (the twinkling stars icon)
+- In a Datadog product integrated with Bits Chat, click {{< ui >}}Ask Bits{{< /ui >}} or {{< img src="bits_ai/dev_agent/twinkling_stars_icon.png" inline="true" style="width:24px">}} (the twinkling stars icon)
- Press Cmd/Ctrl + I
- In the left-side navigation panel, click {{< ui >}}Bits AI{{< /ui >}}
-{{< img src="bits_ai/getting_started/bits_assistant_side_panel.png" alt="Bits AI Assistant side panel showing example prompts" style="width:40%;">}}
+{{< img src="bits_ai/getting_started/bits_assistant_side_panel.png" alt="Bits Chat side panel showing example prompts" style="width:40%;">}}
### Mobile application
-Bits AI Assistant is available on iOS v5.8.4+ and Android v3.15+.
+Bits Chat is available on iOS v5.8.4+ and Android v3.15+.
1. [Download the mobile app and log in][2].
-2. On the home screen, tap {{< ui >}}Bits AI Assistant{{< /ui >}}.
-3. Start chatting with Bits AI Assistant in chat or voice mode.
+2. On the home screen, tap {{< ui >}}Bits Chat{{< /ui >}}.
+3. Start chatting with Bits Chat in chat or voice mode.
{{< img src="bits_ai/getting_started/bitsai_mobile_app.PNG" alt="View of the Mobile App Home dashboard with Bits AI" style="width:40%;" >}}
### Slack
diff --git a/content/en/byoc-logs/introduction/features.md b/content/en/byoc-logs/introduction/features.md
index b836f2cb814..c0c4181f192 100644
--- a/content/en/byoc-logs/introduction/features.md
+++ b/content/en/byoc-logs/introduction/features.md
@@ -26,7 +26,7 @@ The following log features are supported:
**Dashboards and monitors**
- Dashboards with BYOC Logs data
- Log monitors on BYOC Logs indexes
-- Bits AI SRE
+- Bits Investigation
**Index management**
- Multiple indexes with independent retention periods and routing rules
diff --git a/content/en/cloud_cost_management/_index.md b/content/en/cloud_cost_management/_index.md
index fd475a03806..5b49cb3d8b3 100644
--- a/content/en/cloud_cost_management/_index.md
+++ b/content/en/cloud_cost_management/_index.md
@@ -12,7 +12,7 @@ further_reading:
text: "Learn about Tags in Cloud Cost Management"
- link: "/cloud_cost_management/cloud_cost_skill/"
tag: "Documentation"
- text: "Use Cloud Cost skill in Bits AI Assistant"
+ text: "Use Cloud Cost skill in Bits Chat"
- link: "https://www.datadoghq.com/blog/control-your-cloud-spend-with-datadog-cloud-cost-management/"
tag: "Blog"
text: "Gain visibility and control of your cloud spend with Datadog Cloud Cost Management"
@@ -136,9 +136,9 @@ Use this page to troubleshoot data delays or confirm that recent tag pipelines a
## Use AI for cost analysis
-Use the [Cloud Cost Skill in Bits AI Assistant][10] to investigate cost changes, identify likely owners, compare spend against budgets, correlate cost with observability metrics, and create handoff notebooks for engineering teams.
+Use the [Cloud Cost Skill in Bits Chat][10] to investigate cost changes, identify likely owners, compare spend against budgets, correlate cost with observability metrics, and create handoff notebooks for engineering teams.
-{{< img src="cloud_cost/cc_skill_cost_summary.png" alt="Bits AI Assistant's investigation summary showing an initial analysis." style="width:60%;" >}}
+{{< img src="cloud_cost/cc_skill_cost_summary.png" alt="Bits Chat's investigation summary showing an initial analysis." style="width:60%;" >}}
## Further reading
diff --git a/content/en/cloud_cost_management/cloud_cost_skill.md b/content/en/cloud_cost_management/cloud_cost_skill.md
index 647a2f9a971..d040b068e4b 100644
--- a/content/en/cloud_cost_management/cloud_cost_skill.md
+++ b/content/en/cloud_cost_management/cloud_cost_skill.md
@@ -1,13 +1,13 @@
---
-title: Cloud Cost Skill in Bits AI Assistant
-description: Use the Cloud Cost skill in Bits AI Assistant to investigate, explain, and share cloud cost findings.
+title: Cloud Cost Skill in Bits Chat
+description: Use the Cloud Cost skill in Bits Chat to investigate, explain, and share cloud cost findings.
algolia:
tags: ["cloud cost", "cloud cost management", "ccm", "finops", "cloud cost skill", "bits ai assistant", "bits assistant", "mcp"]
rank: 75
further_reading:
- link: "/bits_ai/bits_assistant/"
tag: "Documentation"
- text: "Bits AI Assistant"
+ text: "Bits Chat"
- link: "/bits_ai/mcp_server/"
tag: "Documentation"
text: "Datadog MCP Server"
@@ -20,12 +20,12 @@ further_reading:
---
{{< callout url="https://www.datadoghq.com/product-preview/bits-assistant/" btn_hidden="false" header="Cloud Cost skill is in Preview" >}}
-The Cloud Cost skill runs in Bits AI Assistant. Fill out the Bits AI Assistant Preview form to request access.
+The Cloud Cost skill runs in Bits Chat. Fill out the Bits Chat Preview form to request access.
{{< /callout >}}
## Overview
-The Cloud Cost skill is the Cloud Cost Management analysis workflow in [Bits AI Assistant][1]. It is designed for FinOps tasks, such as root cause analysis, budget tracking, and answering general cost questions. For example, you can ask Bits AI Assistant to:
+The Cloud Cost skill is the Cloud Cost Management analysis workflow in [Bits Chat][1]. It is designed for FinOps tasks, such as root cause analysis, budget tracking, and answering general cost questions. For example, you can ask Bits Chat to:
- Investigate [cost monitor alerts][2], [cost anomalies][3], and [cost changes][4]
- Identify teams, services, accounts, regions, or resources driving spend
@@ -36,11 +36,11 @@ The Cloud Cost skill is the Cloud Cost Management analysis workflow in [Bits AI
## Prerequisites
-To use the Cloud Cost skill in Bits AI Assistant, you must:
+To use the Cloud Cost skill in Bits Chat, you must:
- [Set up Cloud Cost Management][6] for the cost sources you want to analyze
- Have these permissions:
- - [Bits Assistant Access][7] permission
+ - [Bits Chat Access][7] permission
- [Cloud Cost Management permissions][8] for the data you ask about
- (Optional) [Notebook permissions][9], if you want to create or edit investigation [Notebooks][15]
@@ -50,7 +50,7 @@ To use the Cloud Cost skill in Bits AI Assistant, you must:
When you want to start an investigation, such as for a [cost anomaly][3], click {{< ui >}}Investigate{{< /ui >}} or {{< img src="bits_ai/dev_agent/twinkling_stars_icon.png" inline="true" style="width:24px">}} (the twinkling stars icon) to open the Cloud Cost skill.
-Alternatively, you can click {{< ui >}}Ask Bits{{< /ui >}} on the top right of the navigation bar on any Datadog page to open Bits AI Assistant and ask a cost question.
+Alternatively, you can click {{< ui >}}Ask Bits{{< /ui >}} on the top right of the navigation bar on any Datadog page to open Bits Chat and ask a cost question.
Example prompts:
@@ -62,16 +62,16 @@ Example prompts:
### Cost change investigations
-When you investigate a cost change with the Cloud Cost skill, Bits AI Assistant provides a concise summary, then asks what you want to explore next. The initial analysis typically includes:
+When you investigate a cost change with the Cloud Cost skill, Bits Chat provides a concise summary, then asks what you want to explore next. The initial analysis typically includes:
- A daily cost chart for the baseline and investigation periods
- The baseline period, investigation period, total dollar amount and percentage change, and projected annual impact when applicable
- Rate-versus-usage context to help distinguish price changes from consumption changes
- Owner or team attribution based on your cost tags
-{{< img src="cloud_cost/cc_skill_cost_summary.png" alt="Bits AI Assistant's investigation summary showing an initial analysis." style="width:60%;" >}}
+{{< img src="cloud_cost/cc_skill_cost_summary.png" alt="Bits Chat's investigation summary showing an initial analysis." style="width:60%;" >}}
-After the initial summary, Bits AI Assistant can:
+After the initial summary, Bits Chat can:
- Find the top services, accounts, regions, resources, or tags driving the change
- Correlate the cost change with metrics such as CPU requests, memory requests, request count, bucket size, or database usage
@@ -81,14 +81,14 @@ After the initial summary, Bits AI Assistant can:
### Budgets and forecasting
-After setting up [Budgets][5], use the Cloud Cost skill in Bits AI Assistant to explain budget status and spending. Bits AI Assistant can help summarize:
+After setting up [Budgets][5], use the Cloud Cost skill in Bits Chat to explain budget status and spending. Bits Chat can help summarize:
- Actual spend versus budgeted amount
- Forecasted spend versus budgeted amount
- Which cost scope a budget covers, based on the budget's filters
- Which budget entries, teams, services, or providers are contributing to an overage
-After the initial summary, Bits AI Assistant can:
+After the initial summary, Bits Chat can:
- Find the top services, accounts, regions, resources, or tags driving spending
- Identify the teams that own the resources contributing to the cost change
diff --git a/content/en/cloud_cost_management/recommendations/_index.md b/content/en/cloud_cost_management/recommendations/_index.md
index c1fb7bdbb6c..75343fdbb40 100644
--- a/content/en/cloud_cost_management/recommendations/_index.md
+++ b/content/en/cloud_cost_management/recommendations/_index.md
@@ -675,7 +675,7 @@ You can act on recommendations to save money and optimize costs. Cloud Cost Reco
- `-@jira_issues.issue_key:*` - Show only recommendations without a Jira issue
- `jira_issues.issue_key:ABC*` - Filter by specific Jira project prefix
-- **[Bits AI Dev Agent][14] code fixes**: Code fixes are available for applicable S3 and DynamoDB recommendations, as well as the Downsize Kubernetes Deployment recommendation. In these situations, the Bits AI Dev Agent creates production-ready pull requests to implement cloud resource changes and cost optimizations in Terraform or Helm charts, respectively. [Set up the Bits AI Dev Agent][13] to use this feature.
+- **[Bits Code][14] code fixes**: Code fixes are available for applicable S3 and DynamoDB recommendations, as well as the Downsize Kubernetes Deployment recommendation. In these situations, Bits Code creates production-ready pull requests to implement cloud resource changes and cost optimizations in Terraform or Helm charts, respectively. [Set up Bits Code][13] to use this feature.
- **1-click Workflow Automation actions**: Actions are available for a limited set of recommendations, allowing users to execute suggested actions, such as clicking {{< ui >}}Delete EBS Volume{{< /ui >}}, directly within Cloud Cost Management.
- **[Cost Optimization Automation][15]**: Set up automations that act on recommendations continuously on a recurring schedule. Automations are scoped to specific accounts, regions, and tags and include safeguards such as pre-action snapshots and optional human approval through Slack or Microsoft Teams.
- **Datadog Case Management**: Users can go to the recommendation side panel and click {{< ui >}}Create Case{{< /ui >}} to generate a case to manage and take action on recommendations.
diff --git a/content/en/containers/bits_ai_kubernetes_remediation.md b/content/en/containers/bits_ai_kubernetes_remediation.md
index 0b561d1599b..e72685354a3 100644
--- a/content/en/containers/bits_ai_kubernetes_remediation.md
+++ b/content/en/containers/bits_ai_kubernetes_remediation.md
@@ -51,7 +51,7 @@ When a pod is terminated because the memory usage exceeded its limit, you may be
2. Adjust your limit so that it is higher than what your container normally uses.
3. Click {{< ui >}}Fix with Bits AI{{< /ui >}}.
4. On the next page, select the repository where your deployment is defined, and review the proposed changes. Click {{< ui >}}Fix with Bits{{< /ui >}} to create a pull request.
-5. You are redirected to a Bits [Code Session][3], where you can verify that the Bits AI Dev Agent identified the specific configuration file where your memory limits are defined. Click {{< ui >}}Create Pull Request{{< /ui >}} to initiate the creation of the pull request.
+5. You are redirected to a Bits [Code Session][3], where you can verify that Bits Code identified the specific configuration file where your memory limits are defined. Click {{< ui >}}Create Pull Request{{< /ui >}} to initiate the creation of the pull request.
6. Click {{< ui >}}View Pull Request{{< /ui >}} to view the pull request in GitHub.
{{% /collapse-content %}}
diff --git a/content/en/containers/monitoring/_index.md b/content/en/containers/monitoring/_index.md
index 2e14d6d6378..b72a0df3c60 100644
--- a/content/en/containers/monitoring/_index.md
+++ b/content/en/containers/monitoring/_index.md
@@ -33,7 +33,7 @@ Select the [**Autoscaling**][11] tab in the Kubernetes section to view scaling r
### Kubernetes Remediation
-Select the [**Remediation**][13] tab in the Kubernetes section to investigate and remediate errors with [Bits AI Dev Agent][14]. For more information, read the [Bits AI Kubernetes Remediation documentation][15].
+Select the [**Remediation**][13] tab in the Kubernetes section to investigate and remediate errors with [Bits Code][14]. For more information, read the [Bits AI Kubernetes Remediation documentation][15].
{{< callout url="https://www.datadoghq.com/product-preview/kubernetes-remediation/"
btn_hidden="false" header="Join the Preview!">}}
diff --git a/content/en/data_security/data_retention_periods.md b/content/en/data_security/data_retention_periods.md
index e82f71fe079..3f8b044a886 100644
--- a/content/en/data_security/data_retention_periods.md
+++ b/content/en/data_security/data_retention_periods.md
@@ -28,13 +28,13 @@ attributes:
data_type: |
- **Audit logs (Audit Trail enabled)**: 90 days
- **Audit logs (Audit Trail disabled)**: 7 days
- - product: Bits AI Assistant
+ - product: Bits Chat
data_type: |
- **Messages**: 15 months
- - product: Bits AI Dev Agent
+ - product: Bits Code
data_type: |
- **Source Code**: 7 days
- - product: Bits AI SRE
+ - product: Bits Investigation
data_type: |
- **Investigations**: Retained for the duration of the account
- product: Browser RUM
diff --git a/content/en/datadog_cloudcraft/overlays/_index.md b/content/en/datadog_cloudcraft/overlays/_index.md
index 758c9f1af91..f2e435a30e5 100644
--- a/content/en/datadog_cloudcraft/overlays/_index.md
+++ b/content/en/datadog_cloudcraft/overlays/_index.md
@@ -22,7 +22,7 @@ Cloudcraft provides the following built-in overlays:
- [Observability][2]: See where the Datadog Agent is installed and which features are enabled per host.
- [Security][3]: Identify security exposures, misconfigurations, and vulnerabilities in your architecture.
- [Cloud Cost Management (CCM)][4]: Discover savings opportunities with cost recommendations shown directly on resources.
-- [Monitors][5] (Preview): View monitor states for your resources and services, and investigate alerting monitors with Bits AI SRE.
+- [Monitors][5] (Preview): View monitor states for your resources and services, and investigate alerting monitors with Bits Investigation.
- [APM][6]: Visualize distributed APM traces between cloud resources on your diagram (AWS only, Preview).
## Further reading
diff --git a/content/en/datadog_cloudcraft/overlays/monitors.md b/content/en/datadog_cloudcraft/overlays/monitors.md
index 14893cb5330..a34db09ed5f 100644
--- a/content/en/datadog_cloudcraft/overlays/monitors.md
+++ b/content/en/datadog_cloudcraft/overlays/monitors.md
@@ -1,11 +1,11 @@
---
title: Monitors
-description: "Use the Monitors overlay in Cloudcraft to view monitor states for your resources and services, and investigate alerting monitors with Bits AI SRE."
+description: "Use the Monitors overlay in Cloudcraft to view monitor states for your resources and services, and investigate alerting monitors with Bits Investigation."
site_support_id: cloudcraft_monitors_overlay
further_reading:
- link: "/bits_ai/bits_ai_sre/"
tag: "Documentation"
- text: "Bits AI SRE"
+ text: "Bits Investigation"
---
{{< callout btn_hidden="true" header="" >}}
@@ -37,15 +37,15 @@ Use the legend at the bottom of the diagram to filter monitors by alerting statu
### Hover panel
-Hover over a resource or service with monitors to see a count breakdown of associated monitors by status. The hover panel includes an {{< ui >}}Investigate with Bits AI SRE{{< /ui >}} button that loads the three most recent alerting events for the selected monitor. From there, you can initiate an investigation or view an existing one.
+Hover over a resource or service with monitors to see a count breakdown of associated monitors by status. The hover panel includes an {{< ui >}}Investigate with Bits Investigation{{< /ui >}} button that loads the three most recent alerting events for the selected monitor. From there, you can initiate an investigation or view an existing one.
-{{< img src="datadog_cloudcraft/overlays/cloudcraft_monitors_overlay_hover_panel.png" alt="Cloudcraft Monitors overlay hover panel showing a monitor count breakdown by status and the Investigate with Bits AI SRE button." style="width:80%;" >}}
+{{< img src="datadog_cloudcraft/overlays/cloudcraft_monitors_overlay_hover_panel.png" alt="Cloudcraft Monitors overlay hover panel showing a monitor count breakdown by status and the Investigate with Bits Investigation button." style="width:80%;" >}}
-For more information, see [Bits AI SRE][1].
+For more information, see [Bits Investigation][1].
### Side panel
-Click a monitor pin on the diagram to open a side panel listing all monitors associated with that resource or service. For resource monitors, you can also initiate or view a [Bits AI SRE][1] investigation for any alerting monitor from this panel.
+Click a monitor pin on the diagram to open a side panel listing all monitors associated with that resource or service. For resource monitors, you can also initiate or view a [Bits Investigation][1] investigation for any alerting monitor from this panel.
{{< img src="datadog_cloudcraft/overlays/cloudcraft_monitors_overlay_side_panel.png" alt="Cloudcraft Monitors overlay side panel showing a list of monitors associated with a resource." style="width:100%;" >}}
diff --git a/content/en/incident_response/incident_management/investigate/incident_ai.md b/content/en/incident_response/incident_management/investigate/incident_ai.md
index d9adad58ae2..d68e3d4d7a6 100644
--- a/content/en/incident_response/incident_management/investigate/incident_ai.md
+++ b/content/en/incident_response/incident_management/investigate/incident_ai.md
@@ -9,7 +9,7 @@ aliases:
further_reading:
- link: "/bits_ai/bits_ai_sre/"
tag: "Documentation"
- text: "Learn about Bits AI SRE"
+ text: "Learn about Bits Investigation"
- link: "/incident_response/incident_management/post_incident/postmortems"
tag: "Documentation"
text: "Generate AI-assisted postmortems"
@@ -55,11 +55,11 @@ Use natural language prompts to request information or take action from Slack:
| Find related incidents | `@Datadog Are there any related incidents?`
`@Datadog Find me incidents related to DDoS attacks from the past month` |
| Early detection inquiry | `@Datadog A customer is unable to check out. Is there an incident?`
`@Datadog Are there any incidents now impacting the payments service?` |
-## Trigger a Bits AI SRE investigation {#bits-ai-investigation}
+## Trigger a Bits Investigation {#bits-ai-investigation}
-Start a Bits AI SRE investigation directly from your incident Slack channel or the Datadog Incident Management web UI, without leaving your incident response workflow. This reduces context switching during active incidents and allows the AI agent to investigate alongside your team using the same shared context.
+Start a Bits Investigation directly from your incident Slack channel or the Datadog Incident Management web UI, without leaving your incident response workflow. This reduces context switching during active incidents and allows the AI agent to investigate alongside your team using the same shared context.
-Bits AI SRE must be enabled for your organization and you can only trigger an investigation from a **properly configured Datadog Incident Management Slack channel**. The Incident Investigation flow only activates when the system detects a valid incident channel.
+Bits Investigation must be enabled for your organization and you can only trigger an investigation from a **properly configured Datadog Incident Management Slack channel**. The Incident Investigation flow only activates when the system detects a valid incident channel.
**From Slack,** type `@Datadog investigate` in the incident channel to kick off an investigation during an active incident. You can include additional context inline to help the agent narrow its scope from the start:
@@ -70,15 +70,15 @@ Bits AI SRE must be enabled for your organization and you can only trigger an in
When triggered, the agent automatically pulls in the incident's timeline, linked telemetry signals (traces, metrics, and logs), and any context you provide in the prompt. It then posts updates back to the channel as a thread reply, with a final root cause summary and recommended next steps surfaced to the broader channel when the investigation completes.
-{{< img src="incident_response/incident_management/incident_ai/Triggering_investigations_slack.png" alt="A Datadog incident Slack channel showing a completed Bits AI SRE investigation with root cause findings and a View Full Investigation button" >}}
+{{< img src="incident_response/incident_management/incident_ai/Triggering_investigations_slack.png" alt="A Datadog incident Slack channel showing a completed Bits Investigation with root cause findings and a View Full Investigation button" >}}
**From the web UI**, you can trigger an investigation directly from the "Investigation" section on the incident overview page.
-{{< img src="incident_response/incident_management/incident_ai/Triggering_investigations_web.png" alt="The Incident Management overview page showing a completed Bits AI SRE investigation in the Investigation section with a View Full Investigation button" >}}
+{{< img src="incident_response/incident_management/incident_ai/Triggering_investigations_web.png" alt="The Incident Management overview page showing a completed Bits Investigation in the Investigation section with a View Full Investigation button" >}}
-When triggered, the investigation is embedded in the incident web UI, and Bits AI SRE appears as a responder in the Responder Roles section of the page.
+When triggered, the investigation is embedded in the incident web UI, and Bits Investigation appears as a responder in the Responder Roles section of the page.
-For a full walkthrough of the investigation workflow, see [Bits AI SRE][4].
+For a full walkthrough of the investigation workflow, see [Bits Investigation][4].
## Further reading
diff --git a/content/en/mobile/_index.md b/content/en/mobile/_index.md
index a5efb7e4b67..c7878392ad7 100644
--- a/content/en/mobile/_index.md
+++ b/content/en/mobile/_index.md
@@ -100,7 +100,7 @@ To log out, navigate to the **Settings** page on the mobile app and click on **L
The On-Call page provides a comprehensive view of On-Call shifts, schedules, pages, and escalation policies. You can filter the information by user, team, urgency, status, or date to quickly find relevant details. Tapping **Escalate** prompts you to confirm the escalation to the next policy level. Tapping **Declare Incident** prompts you to enter a title and provide relevant incident attributes.
-You can initiate a page to an individual or team, and also override existing shifts by tapping on the shift you would like to override. You can view Bits AI SRE monitor investigations for initial findings and conclusions. For more information, see [Datadog On-Call][20].
+You can initiate a page to an individual or team, and also override existing shifts by tapping on the shift you would like to override. You can view Bits Investigation monitor investigations for initial findings and conclusions. For more information, see [Datadog On-Call][20].
To configure On-Call notifications on your mobile device, see the guide to [Set up your Mobile Device for Datadog On-Call][21].
@@ -287,23 +287,23 @@ On the Services page, you can view, search and filter all services that you have
{{% /tab %}}
{{< /tabs >}}
-On the Bits AI home page, you can ask questions about your organization's system health. Bits AI supports natural language querying for logs and APM traces. For more information, see [Bits AI Assistant][27].
+On the Bits AI home page, you can ask questions about your organization's system health. Bits AI supports natural language querying for logs and APM traces. For more information, see [Bits Chat][27].
-### Bits AI SRE
+### Bits Investigation
{{< tabs >}}
{{% tab "iOS" %}}
-{{< img src="service_management/mobile/ios_bits_sre.png" style="width:100%; background:none; border:none; box-shadow:none;" alt="Bits AI SRE investigation results displayed on an On-Call page">}}
+{{< img src="service_management/mobile/ios_bits_sre.png" style="width:100%; background:none; border:none; box-shadow:none;" alt="Bits Investigation results displayed on an On-Call page">}}
{{% /tab %}}
{{% tab "Android" %}}
-{{< img src="service_management/mobile/android_bits_sre.png" style="width:100%; background:none; border:none; box-shadow:none;" alt="Bits AI SRE investigation results displayed on an On-Call page">}}
+{{< img src="service_management/mobile/android_bits_sre.png" style="width:100%; background:none; border:none; box-shadow:none;" alt="Bits Investigation results displayed on an On-Call page">}}
{{% /tab %}}
{{< /tabs >}}
-When enabled, Bits AI SRE initiates investigations directly on On-Call pages. These investigations present initial findings and conclusions to help responders identify potential root causes and next steps. For more information, see [Bits AI SRE][28].
+When enabled, Bits Investigation initiates investigations directly on On-Call pages. These investigations present initial findings and conclusions to help responders identify potential root causes and next steps. For more information, see [Bits Investigation][28].
## Frequently Asked Question
### How do I remain logged into the mobile app?
diff --git a/content/en/security/code_security/_index.md b/content/en/security/code_security/_index.md
index 01cf7556127..38aa8191f3f 100644
--- a/content/en/security/code_security/_index.md
+++ b/content/en/security/code_security/_index.md
@@ -4,7 +4,7 @@ disable_toc: false
further_reading:
- link: "https://www.datadoghq.com/blog/bitsai-dev-agent-code-security"
tag: "Blog"
- text: "Introducing Bits AI Dev Agent for Code Security"
+ text: "Introducing Bits Code for Code Security"
- link: "https://www.datadoghq.com/blog/remediate-faster-code-security"
tag: "Blog"
text: "Remediate transitive vulnerabilities faster with Datadog Software Composition Analysis"
diff --git a/content/en/security/code_security/static_analysis/_index.md b/content/en/security/code_security/static_analysis/_index.md
index f7cdf3141e1..411d9477345 100644
--- a/content/en/security/code_security/static_analysis/_index.md
+++ b/content/en/security/code_security/static_analysis/_index.md
@@ -9,7 +9,7 @@ algolia:
further_reading:
- link: "https://www.datadoghq.com/blog/bitsai-dev-agent-code-security"
tag: "Blog"
- text: "Introducing Bits AI Dev Agent for Code Security"
+ text: "Introducing Bits Code for Code Security"
- link: https://www.datadoghq.com/blog/code-security-secret-scanning
tag: Blog
text: Detect and block exposed credentials with Datadog Secret Scanning
diff --git a/content/en/security/code_security/static_analysis/ai_enhanced_sast.md b/content/en/security/code_security/static_analysis/ai_enhanced_sast.md
index 0ae3f64badc..a4607f8edc7 100644
--- a/content/en/security/code_security/static_analysis/ai_enhanced_sast.md
+++ b/content/en/security/code_security/static_analysis/ai_enhanced_sast.md
@@ -13,7 +13,7 @@ further_reading:
text: 'Using LLMs to filter out false positives from static code analysis'
- link: "https://www.datadoghq.com/blog/bitsai-dev-agent-code-security"
tag: "Blog"
- text: "Introducing Bits AI Dev Agent for Code Security"
+ text: "Introducing Bits Code for Code Security"
---
Static Code Analysis (SAST) uses AI to help automate detection, validation, and remediation across the vulnerability management lifecycle.
@@ -145,7 +145,7 @@ Each finding includes a section with an explanation of the assessment. You can p
## Remediation
-Datadog SAST uses the [Bits AI Dev Agent][10] to generate code fixes for vulnerabilities. You can remediate individual vulnerabilities or fix multiple vulnerabilities using bulk remediation campaigns.
+Datadog SAST uses the [Bits Code][10] to generate code fixes for vulnerabilities. You can remediate individual vulnerabilities or fix multiple vulnerabilities using bulk remediation campaigns.
To view and remediate vulnerabilities:
@@ -170,7 +170,7 @@ Selecting this option opens a **Create a new Bits AI Bulk Fix Campaign** modal w
- **PR grouping options**: How Bits AI should group findings into pull requests (for example, one PR per repository, file, or finding). You can also limit the number of open PRs and the number of findings per PR.
- **Custom instructions** (optional): Additional guidance for how Bits AI should generate fixes, such as changelog requirements or pull request title formatting.
-After you create a campaign, Bits AI Dev Agent loads the in-scope findings, generates patches based on your grouping rules, and (if enabled) creates pull requests. You can review and edit each session before merging changes.
+After you create a campaign, Bits Code loads the in-scope findings, generates patches based on your grouping rules, and (if enabled) creates pull requests. You can review and edit each session before merging changes.
@@ -181,11 +181,11 @@ After you create a campaign, Bits AI Dev Agent loads the in-scope findings, gene
#### View campaign progress
-To view all campaigns, navigate to [**Bits AI** > **Dev Agent** > **Code Sessions** > **Campaigns**][12].
+To view all campaigns, navigate to [**Bits AI** > **Bits Code** > **Code Sessions** > **Campaigns**][12].
-Click a campaign to view details including session status, pull requests by repository, and remediated findings. You can click on individual sessions to review, edit, and merge fixes with the [Bits AI Dev Agent][10].
+Click a campaign to view details including session status, pull requests by repository, and remediated findings. You can click on individual sessions to review, edit, and merge fixes with the [Bits Code][10].
-{{< img src="/code_security/static_analysis/campaigner-hero-image.png" alt="Campaigns page in Bits AI Dev Agent" style="width:100%;">}}
+{{< img src="/code_security/static_analysis/campaigner-hero-image.png" alt="Campaigns page in Bits Code" style="width:100%;">}}
### Remediation session details
@@ -200,7 +200,7 @@ To open the remediation session, select the vulnerability from the [**Vulnerabil
You can also navigate to remediation sessions through the [**Campaigns**][12] and [**Code Sessions**][7] views.
-{{< img src="/code_security/static_analysis/single-session-sql-injection-fix-light-png.png" alt="Concluded remediation session in Bits AI Dev Agent showing generated fixes and pull request options" style="width:100%;">}}
+{{< img src="/code_security/static_analysis/single-session-sql-injection-fix-light-png.png" alt="Concluded remediation session in Bits Code showing generated fixes and pull request options" style="width:100%;">}}
## Further reading
diff --git a/content/en/tests/flaky_management/_index.md b/content/en/tests/flaky_management/_index.md
index 8818a0bda8c..084570205ff 100644
--- a/content/en/tests/flaky_management/_index.md
+++ b/content/en/tests/flaky_management/_index.md
@@ -156,7 +156,7 @@ This method avoids unnecessary CI failures and saves developer time.
## AI-powered flaky test fixes
-Bits AI Dev Agent can automatically diagnose and fix flaky tests that have been detected by Test Optimization. When a flaky test is identified, Bits AI analyzes the test failure patterns and generates production-ready fixes that can be submitted as GitHub pull requests.
+Bits Code can automatically diagnose and fix flaky tests that have been detected by Test Optimization. When a flaky test is identified, Bits AI analyzes the test failure patterns and generates production-ready fixes that can be submitted as GitHub pull requests.
For Bits AI to create a fix, the flaky test must meet the following criteria:
- **Failure rate**: At least 5%
@@ -164,11 +164,11 @@ For Bits AI to create a fix, the flaky test must meet the following criteria:
- **Failed pipelines**: At least 2 pipelines
- **Branch**: Must have flaked in the default branch
-{{< img src="tests/bits_ai_flaky_test_fixes-2.png" alt="Bits AI Dev Agent displaying a proposed fix for a flaky test" style="width:100%;" >}}
+{{< img src="tests/bits_ai_flaky_test_fixes-2.png" alt="Bits Code displaying a proposed fix for a flaky test" style="width:100%;" >}}
### Setup
-To enable AI-powered flaky test fixes, enable Bits AI Dev Agent for Test Optimization by following the setup instructions in the [Bits AI Dev Agent documentation][16]. Bits AI Dev Agent automatically create fixes for flaky tests detected by Test Optimization.
+To enable AI-powered flaky test fixes, enable Bits Code for Test Optimization by following the setup instructions in the [Bits Code documentation][16]. Bits Code automatically create fixes for flaky tests detected by Test Optimization.
A flaky test must have at least one failed execution that includes both @error.message and @test.source.file tags to be eligible for a fix. Generating a fix may take some time.