This product is not supported for your selected
Datadog site. (
).
Start a Bits investigation
You can launch a Bits investigation from several entry points in the Datadog UI:
You can also use Bits Investigation from AI assistants, applications, and the command line. For more information, see the MCP, API, CLI page.
Monitor alerts
You can invoke Bits on an individual monitor alert or warn event from several entry points:
Option 1: Bits Investigation Monitors list
- Go to Bits Investigation > Monitors > Supported.
- Click Investigate Recent Alerts and select an alert.
Option 2: Monitor status page
Navigate to the monitor status page of a Bits Investigation-supported monitor and click Investigate with Bits Investigation in the top-right corner.
Option 3: Monitor event side panel
In the monitor event side panel of a Bits Investigation-supported monitor, click Investigate with Bits Investigation.
Option 4: Slack
To use the Slack integration, connect your Slack workspace to Bits Investigation.
In Slack, reply to a monitor notification with @Datadog Investigate this alert.
Option 5: Microsoft Teams
To receive investigation findings in Microsoft Teams, send monitor notifications to a Microsoft Teams channel.
Synthetic tests
When a Synthetic Browser or API test monitor triggers, you can launch a Bits investigation to identify the root cause. Bits 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
- On the Synthetic Tests page, open the Synthetic test you want to investigate and go to the Timeline section.
- Select the Alert Triggered event for the failing test run.
- Click Investigate with Bits.
The investigation opens in a new page, and you can also view it from the test details page after it runs.
From a Synthetic monitor
Synthetic monitors support the same monitor-based entry points as other supported monitor types. See Monitor alerts for the available options, or toggle Auto-Investigate on a Synthetic monitor to start investigations automatically. For details, see Enable automatic investigations.
Real User Monitoring
You can launch a Bits investigation from several places in Real User Monitoring (RUM):
Error Tracking
Preview
Bits Investigation in Error Tracking is in Preview.
You can launch a Bits investigation from an Error Tracking issue. To start an investigation, click Investigate this issue on the Review tab of the issue panel. Bits analyzes the error, its stack trace, and related telemetry. If you set up Source Code Integration, Bits also analyzes your source code. It then summarizes the root cause and impact in the issue panel. For details, see Investigate Errors with Bits AI.
General prompt
Click on New Investigation and describe the issue you want to troubleshoot. Include as much relevant context as possible:
- Observed symptoms (e.g., errors, latency) including any links to Datadog telemetry that indicate this
- Relevant tags such as service, application, or environment that isolate the issue
- A time window (default is past 4 hours)
The more specific your prompt, the more accurate and useful the investigation will be.
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 Investigation automatically uses the entire thread as investigation context.
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 Investigation Monitors list
- Go to Bits Investigation > Monitors > Supported.
- Toggle Auto-Investigate on for a single monitor, or bulk-edit multiple monitors by selecting multiple monitors, then clicking Auto-Investigate All.
For a single monitor
- Open the monitor’s status page and click Edit.
- Scroll to Configure notifications & automations and toggle Investigate with Bits Investigation.
- You can't enable automatic investigations on a monitor through the Datadog API or Terraform. To trigger an individual investigation programmatically, see MCP, API, CLI.
- 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.
Supported monitors
Bits is able to run investigations on the following monitor types:
- Metric
- Anomaly
- Forecast
- Integration
- Outlier
- Logs
- APM (
APM Metrics type only; Trace Analytics is not supported) - Composites. For automatic investigations:
- At least one child monitor must be a supported type.
- Metric and log child monitors count only if the child monitor has a
service tag, or its query filters or groups by service.
- SLOs
- Synthetics API and Browser tests
- RUM
How Bits investigates
When Bits 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 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.
At the end of an investigation, Bits either presents a clear, evidence-backed conclusion or marks the investigation as inconclusive when the available data is insufficient to support a defensible conclusion.
When Bits reaches a conclusion, it suggests next steps, such as a code fix, a triage action, or an infrastructure action. For details, see Bits Remediation.
Supported data sources
Bits uses the following data sources during investigations:
Datadog products
- Metrics
- APM traces
- Logs
- Dashboards
- Events
- Change Tracking
- Source code (GitHub only)
- Watchdog
- Real User Monitoring
- Error Tracking
- Network Path
- Database Monitoring
- Continuous Profiler
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 correlate data more accurately.
Third-party integrations
- Grafana
- Dynatrace
- Sentry
- Splunk
- ServiceNow
- Confluence
Third-party integrations are in Preview for all customers.
For best practices on maximizing the effectiveness of investigations, see Knowledge sources.
Investigation display modes
There are two display modes: Investigation Steps and Hypothesis Tree.
While an investigation is in progress, Bits captures every step it takes—including how it evaluates evidence and makes decisions—in the Investigation Steps view. This provides a real-time, detailed record of the agent’s reasoning process.
Once the investigation is complete, you can switch to the Hypothesis Tree view to explore a structured, tree-based visualization of the investigative path, making it easier to understand findings and conclusions at a glance.
Reports
The Reports 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.
Further reading
Additional helpful documentation, links, and articles: