- 필수 기능
- 시작하기
- 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+=`In the heat of an incident, Bits AI SRE handles general incident coordination so you can focus on resolution. From proactive updates to AI-assisted postmortems, Bits streamlines your incident response workflow in Slack and Datadog.
Bits AI SRE helps coordinate incidents—especially those involving multiple teams—by suggesting next steps throughout the incident lifecycle. This streamlines communication and improves overall process management.
/dd connect
command.@Datadog
command.Bits can dynamically populate key details in stakeholder notifications—delivering clearer, faster updates across the tools your team already uses. Notification rules support delivery to a wide variety of destinations, including email, Datadog On-Call, MS Teams, Slack, and more, ensuring AI-enhanced updates reach the right people—on the right platform—at the right time.
Field | Variable |
---|---|
AI Contributing Factors | {{incident.ai_contributing_factors}} |
AI Impact | {{incident.ai_impact}} |
AI Issue | {{incident.ai_issue}} |
AI Remediation | {{incident.ai_remediation}} |
When you join an incident channel in Slack (connected to Datadog Incident Management), Bits automatically posts a summary containing key information about the incident such as the contributing factors, impact, issue, and remediation. This summary is only visible to you.
When an incident is changed to resolved, Bits posts a final summary. This is visible to everyone in the channel.
Bits automatically flags related incidents if they are declared within 20 minutes of each other, helping you identify broader systemic issues.
Use natural language prompts to request for information or take action from Slack:
Functionality | Example prompt |
---|---|
Declare an incident | @Datadog Declare an incident |
Change severity | @Datadog Update this incident to SEV-3 |
Change status | @Datadog Mark this incident as stable @Datadog Resolve this incident |
Request new summary | @Datadog Give me a summary of this incident @Datadog Summarize incident-262 Note: Private incidents are not summarized. |
Search incident history | @Datadog How many incidents are currently ongoing? @Datadog Show me all Sev-1 incidents that occurred in the past week. |
Dive into specific incidents | @Datadog What was the root cause of incident-123? Or@Datadog What remediation actions did the responders take in incident-123? |
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? |
Draft a Datadog Status Page update | @Datadog Create a Status Page |
After an incident is resolved, Bits collects any follow-up tasks responders mentioned during the incident. It then prompts you to review and create them with a single click. These tasks are saved as Incident Follow-Ups in Datadog Incident Management.
To view suggested follow-up tasks:
Description | Variable |
---|---|
Executive summary | {{incident.ai_summary}} |
System context and dependencies | {{incident.ai_system_overview}} |
Key event timeline | {{incident.ai_key_timeline}} |
Summary of customer impact | {{incident.ai_customer_impact}} |
Follow-up actions | {{incident.ai_action_items}} |
Key takeaways for future prevention | {{incident.ai_lessons_learned}} |
Note: AI variables must be preceded by a section header.
To generate an AI-assisted postmortem draft:
추가 유용한 문서, 링크 및 기사: