- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
",t};e.buildCustomizationMenuUi=t;function n(e){let t='
",t}function s(e){let n=e.filter.currentValue||e.filter.defaultValue,t='${e.filter.label}
`,e.filter.options.forEach(s=>{let o=s.id===n;t+=``}),t+="${e.filter.label}
`,t+=`There are two main ways to enable Bits for automated investigations:
bitsai:enabled
tag to your selected monitors.You can also add the tag to your desired monitors using the Datadog API or Terraform.
Bits can send investigation results to several destinations. By default, results appear in two places:
Additionally, if you have already configured @slack
, @oncall
, or @case
notifications in your monitor, Bits automatically writes to those places. If not, you can add them as destinations for investigation results to appear:
@slack-{channel-name}
handle to send results to Slack.In the Configure notifications and automations section, add the @oncall-{team} handle.
In the Configure notifications and automations section, add the @case-{project-name}
handle.
Alternatively, you can manually invoke Bits on an individual monitor event.
@Datadog Investigate this alert
.For best results, see Optimize monitors for Bits AI SRE.
To help Bits produce the most accurate and helpful investigation results, follow these guidelines:
Investigations happen in two phases:
For best results, see Optimize monitors for Bits AI SRE.
On the Bits AI Investigations page, you can chat with Bits to gather additional information about the investigation or the services involved. Click the Suggested replies bubble for examples.
Functionality | Example prompts | Data source |
---|---|---|
Understand the status of its investigation | What's the latest status of the investigation? | Investigation findings |
Ask for elaborations of its findings | Tell me more about the {issue}. | Investigation findings |
Look up information about a service | Are there any ongoing incidents for {example-service}? | Software Catalog service definitions |
Find recent changes for a service | Were there any recent changes on {example-service}? | Change Tracking events |
Find a dashboard | Give me the {example-service} dashboard. | Dashboards |
Query APM request, error, and duration metrics | What's the current error rate for {example-service}? | APM metrics |
Search for information in Confluence | Find me the runbook in Confluence to rollback deployments for {example-service}. | Confluence |
Reviewing Bits’ findings not only validates their accuracy, but also helps Bits learn from any mistakes it makes, enabling it to produce faster and more accurate investigations in the future.
You can guide Bits’ learning by:
At the end of an investigation, let Bits know if the conclusion it made was correct or not. If it was inaccurate, provide Bits with the correct root cause so that it can learn from the discrepancy.
Every piece of feedback you give generates a memory. Bits uses these memories to enhance future investigations by recalling relevant patterns, queries, and corrections. You can navigate to Bits-Enabled Monitors to view and delete memories in the Memories column.