Database Investigations in Bits Chat
이 페이지는 아직 한국어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우
언제든지 연락주시기 바랍니다.Database Monitoring contributes a set of tools and skills to Bits Chat, so you can investigate the databases you monitor directly in chat. Bits Chat analyzes the telemetry Database Monitoring already collects. This includes health signals, query metrics, explain plans, instance and infrastructure metrics, calling APM services, related incidents, and recent events. For a database investigation, Bits Chat returns a structured root cause analysis with concrete remediation steps.
Bits Chat supports investigating all databases monitored by Database Monitoring.
Both database administrators and the platform or application teams that own database-backed services can investigate this way. Describe an issue in plain language and Bits Chat runs the investigation. Deep database expertise is not required.
Use Bits Chat to answer questions like:
Why is this database slow?What caused the latency spike on this query in the last hour?Is this regression isolated to one instance or fleet-wide?Which upstream service is driving the workload change?How can I reduce lock contention on this table?
Database investigations are billed in AI Credits.
Start an investigation
Start a database investigation from any of the following surfaces in Database Monitoring:
- The Investigate button on a database Overview page
- A metric in the Metrics tab of a database host
- A Blocking Queries or Deadlocks panel
- A normalized query in Query Metrics
- A query sample in Query Samples
Each of these automatically launches a Bits Chat session and starts an investigation scoped to what you clicked from. You do not need to write a prompt.
You can also ask a database question from anywhere in Datadog. Click Ask Bits in the top-right of the navigation bar, or press Cmd/Ctrl + I.
Bits Chat streams the response as it works through the investigation. It states a plan, calls Datadog services to gather evidence, and shares interim findings. The investigation ends with a structured report covering what happened, why, the supporting evidence, the root cause, and recommended fixes.
You can ask follow-up questions at any point to refine the analysis. You can also paste in external context, such as an execution plan captured outside of Datadog, and Bits Chat factors it into its next steps.
If a recommended fix involves a SQL change (a new index, a query rewrite), Bits Chat includes the SQL in its response. Bits Chat never connects to your database or runs SQL against it, as recommended changes are for you to review and apply.
Share, save, or escalate findings
After an investigation completes, you can:
- Share the conversation: copy the URL to deep-link a teammate into the same conversation.
- Export to a notebook: capture the investigation in a Datadog notebook for write-up, follow-up, or sharing in a postmortem.
- Create an incident: escalate the findings into a new Datadog incident.
Permissions
To run database investigations, your role must have the Bits Chat Access and Database Monitoring Read permissions. Bits Chat uses your Datadog role to fetch data, so it can only access the resources you have permission to view.
Programmatic access
The data sources that Bits Chat uses for database investigations are also exposed through the Datadog MCP server. You can call them from your own AI tooling.
Preview investigations
Investigations you ran in Database Investigator during Preview, before database investigations moved into Bits Chat, are kept separately from your Bits Chat conversation history. They remain available until September 30, 2026.
To reach them, click the dropdown arrow next to the Investigate button in Database Monitoring, then select View Preview Investigations.
The Preview Investigations panel lists your past investigations. Open one to view it, share it, or export it to a Datadog notebook.
Further reading
