| Field | -Variable | -
|---|---|
| AI Contributing Factors | -{{incident.ai_contributing_factors}} |
-
| AI Impact | -{{incident.ai_impact}} |
-
| AI Issue | -{{incident.ai_issue}} |
-
| AI Remediation | -{{incident.ai_remediation}} |
-
Note: AI variables must be preceded by a section header.
-1. Click **Save**. Your new template appears as a template option during postmortem generation. - -## Generate a first draft of the incident postmortem - -To generate an AI-assisted postmortem draft: -1. In Datadog, navigate to the resolved incident you'd like to generate a postmortem for. -1. Ensure the incident timeline contains at least 10 messages. -1. Click **Generate Postmortem**. -1. Under **Choose Template**, select either the out-of-the-box **General incident with AI content** template, or a custom template that you've created. -1. Click **Generate**. Allow up to one minute for the postmortem to be generated. Do not close the tab during this time. -1. Review the AI-generated postmortem draft. It serves as a starting point for your incident responders. Datadog recommends reviewing and refining the draft before sharing it. - -For more information on generating and managing postmortems, see [Incident Postmortems][6]. +For a full walkthrough of the investigation workflow, see [Bits AI SRE][4]. ## Further reading {{< partial name="whats-next/whats-next.html" >}} -[1]: https://app.datadoghq.com/incidents/settings?section=message-templates -[2]: https://app.datadoghq.com/incidents/settings?section=notification-rules -[3]: https://app.datadoghq.com/incidents/settings?section=postmortem-templates -[4]: https://app.datadoghq.com/incidents/settings?section=integrations -[5]: /incident_response/incident_management/post_incident/follow-ups -[6]: /incident_response/incident_management/post_incident/postmortems -[7]: /integrations/slack/?tab=datadogforslack -[8]: /bits_ai/bits_ai_sre +[1]: /incident_response/incident_management/setup_and_configuration/integrations/slack +[2]: /incident_response/incident_management/setup_and_configuration/templates +[3]: /incident_response/incident_management/post_incident/postmortems +[4]: /bits_ai/bits_ai_sre diff --git a/content/en/incident_response/incident_management/post_incident/follow-ups.md b/content/en/incident_response/incident_management/post_incident/follow-ups.md index 116a664da68..2bbab3a9891 100644 --- a/content/en/incident_response/incident_management/post_incident/follow-ups.md +++ b/content/en/incident_response/incident_management/post_incident/follow-ups.md @@ -28,6 +28,14 @@ Common examples for creating follow-ups include: By capturing these items as follow-ups, your team can stay focused on incident resolution while ensuring important improvements aren't forgotten. +## AI-suggested follow-up tasks + +After an incident is resolved, Incident AI scans the incident channel for follow-up tasks that responders mentioned during the incident. It then prompts you to review and create them with a single click. Tasks saved this way appear as Incident Follow-ups in Datadog Incident Management. + +To view AI-suggested follow-up tasks: +1. Navigate to the relevant incident in Datadog. +1. Open the **Post-Incident** tab to view a list of all follow-up tasks saved from Slack. + ## Create and manage follow-ups Follow-ups can be created at any point during an incident (even before it's resolved), allowing responders to document necessary work as they discover it. After resolution, you can [export follow-ups](#export-follow-ups) to Jira or Case Management to integrate them into your team's existing workflows. @@ -64,7 +72,6 @@ After defining an export template, you have two options: ### Case Management exports - When you export your follow-ups to [Case Management][2], you can manage, track, and analyze your follow-ups directly in Datadog. For example, you can: * View all of the open follow-up cases assigned to a particular user in Datadog diff --git a/content/en/incident_response/incident_management/post_incident/postmortems.md b/content/en/incident_response/incident_management/post_incident/postmortems.md index 06a70a8a6c6..ca281655711 100644 --- a/content/en/incident_response/incident_management/post_incident/postmortems.md +++ b/content/en/incident_response/incident_management/post_incident/postmortems.md @@ -68,7 +68,8 @@ Use the **Save Location** dropdown in the template editor to select where the ge Templates support variables that populate with incident data when the postmortem is generated. Variables allow you to include relevant incident context automatically without copying it manually. For a full list of available variables, see the [Incident Variables][6] reference. -**Standard variables** pull directly from incident fields: +{{% collapse-content title="Standard variables" level="h4" %}} +Standard variables pull directly from incident fields and also include any defined [custom property fields][5]. | Variable | Description | |---|---| @@ -77,12 +78,38 @@ Templates support variables that populate with incident data when the postmortem | `{{incident.severity}}` | The incident severity level | | `{{incident.commander}}` | The incident commander's name, or their email or handle if no name is set | -Any [custom property fields][5] you have defined are also available as variables. +{{% /collapse-content %}} + +{{% collapse-content title="Incident card variable" level="h4" %}} +The incident card variable (`{{incident.card}}`) embeds a summary card that reflects incident fields in real time. When incident fields change, the card in the postmortem updates automatically. -**The incident card variable** (`{{incident.card}}`) embeds a summary card that reflects incident fields in real time. When incident fields change, the card in the postmortem updates automatically, reducing the need to switch between the two. **Note**: The incident card is only supported in Datadog Notebooks. +{{% /collapse-content %}} + +{{% collapse-content title="AI variables" level="h4" %}} +AI variables use Bits AI to generate suggested content based on incident data. When you generate a postmortem that includes an AI variable, Datadog provides a suggested value that you can accept, edit, or reject before it is saved. + +| Variable | Description | +|---|---| +| `{{incident.ai_summary}}` | Executive summary | +| `{{incident.ai_system_overview}}` | System context and dependencies | +| `{{incident.ai_key_timeline}}` | Key event timeline | +| `{{incident.ai_customer_impact}}` | Summary of customer impact | +| `{{incident.ai_action_items}}` | Follow-up actions | +| `{{incident.ai_lessons_learned}}` | Key takeaways for future prevention | + +To use these variables: +1. Create or edit a postmortem template in [**Incident Management Settings > Post-Mortem Templates**][4]. +1. Add the variables to the template body. +1. When generating a postmortem, select the **General incident with AI content** out-of-the-box template, or a custom template that includes AI variables. +1. Allow up to one minute for AI-generated content to populate. Datadog recommends reviewing and refining AI-generated content before sharing the postmortem. + +**Note**: +- AI variables must be preceded by a section header. +- The incident timeline must contain at least 10 messages for AI variables to generate content. + -**AI variables** use Bits AI to generate suggested content based on incident data. When you generate a postmortem that includes an AI variable, Datadog provides a suggested value that you can accept, edit, or reject before it is saved. The `{{incident.ai_summary}}` variable, for example, generates a suggested summary of what occurred during the incident. +{{% /collapse-content %}} ## Attach an existing postmortem diff --git a/content/en/incident_response/incident_management/setup_and_configuration/templates.md b/content/en/incident_response/incident_management/setup_and_configuration/templates.md index 624e1998927..e1e12507125 100644 --- a/content/en/incident_response/incident_management/setup_and_configuration/templates.md +++ b/content/en/incident_response/incident_management/setup_and_configuration/templates.md @@ -33,6 +33,19 @@ To create a message template: **Note:** Template variables are supported in both the message's title and body. +### AI variables for notifications + +Incident AI can dynamically populate key details in notifications with AI-generated content. Insert any of the following variables into your message body: + +| Field | Variable | +|---|---| +| AI Contributing Factors | `{{incident.ai_contributing_factors}}` | +| AI Impact | `{{incident.ai_impact}}` | +| AI Issue | `{{incident.ai_issue}}` | +| AI Remediation | `{{incident.ai_remediation}}` | + +{{< img src="service_management/incidents/incident_ai/message_template_variables.png" alt="New message template with AI variables in it" style="width:80%;" >}} + ## Postmortems Postmortem templates are dynamic, reusable templates used to create a postmortem that is automatically populated with incident information after an incident has been resolved. Postmortem templates use [template variables][4], such as `{{incident.severity}}`, to dynamically inject the corresponding value from the incident that the postmortem is being created for. @@ -46,6 +59,21 @@ To create a postmortem template: 5. (Optional) Set the template as the default. 6. Click **Save**. +### AI variables for postmortems + +Postmortem templates support AI variables that use Bits AI to generate suggested content based on incident data. When you generate a postmortem that includes an AI variable, Datadog provides a suggested value to accept, edit, or reject. + +**Note**: AI variables must be preceded by a section header. + +| Variable | Description | +|---|---| +| `{{incident.ai_summary}}` | Executive summary | +| `{{incident.ai_system_overview}}` | System context and dependencies | +| `{{incident.ai_key_timeline}}` | Key event timeline | +| `{{incident.ai_customer_impact}}` | Summary of customer impact | +| `{{incident.ai_action_items}}` | Follow-up actions | +| `{{incident.ai_lessons_learned}}` | Key takeaways for future prevention | + For more information on generating postmortems using these templates, see [Incident Postmortems][5]. ## Further reading