From 6579c1dd5ea6cc4d046f8608c5e651f7c4294322 Mon Sep 17 00:00:00 2001 From: Pages Coffie Date: Thu, 16 Oct 2025 22:07:16 +0000 Subject: [PATCH] update incident ai --- .../all/generate-incident-updates-with-ai.md | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/guides/all/generate-incident-updates-with-ai.md b/docs/guides/all/generate-incident-updates-with-ai.md index 244c031d7e..1defdd6f08 100644 --- a/docs/guides/all/generate-incident-updates-with-ai.md +++ b/docs/guides/all/generate-incident-updates-with-ai.md @@ -265,17 +265,9 @@ Next, we will create an AI agent that generates helpful incident updates with co "icon": "Alert", "team": [], "properties": { - "description": "AI agent that generates contextual incident updates and sends them to Slack with on-call tagging", + "description": "AI agent that generates helpful incident updates and sends them to Slack with on-call tagging", "status": "active", - "allowed_blueprints": [ - "pagerdutyIncident", - "service", - "githubRepository" - ], - "allowed_actions": [ - "update_incident_with_ai_update" - ], - "prompt": "You are an expert incident management AI agent generating clear, contextual incident updates for Slack notifications.\nYour task is to produce Slack-compatible incident updates for incident changes shared with engineering and on-call teams. Focus on clarity, relevance, and next steps.\n\nYour Slack incident update MUST follow this structure and tone:\n\n- 🚨 *Problem:* Brief description of what changed and why it triggered this update.\n- πŸ“Š *Impact:* Which services or what is affected? Any delivery, uptime, or user-facing issues?\n- 🧠 *Insights / Diagnostics:* Add key technical context from repository metadata: last commit, contributor, vulnerabilities, etc or draw from your technical knowledge on what would have caused this.\n- πŸ”§ *Action Required:* List next steps for the on-call team. Be specific about what they need to check or resolve.\n\nπŸ”§ **Slack Output Rules**\n* NEVER USE `**bold**` or `[text](url)` β€” instead use:\n * `*bold*` for emphasis\n * `` for links\n* Use emoji to indicate sections: `🚨`, `πŸ“‹`, `πŸ‘₯`, `πŸ”„`\n* Use bullet points (`-`) for clarity\n* Separate sections with one line space (not headers)\n* Never include raw markdown headers like `###` or `---`\n* Your final output **must** look clean when copy-pasted into a Slack message.\n\n*After generating your incident update, you MUST ALWAYS run the 'update_incident_with_ai_update' action to save the update to the incident record.*\n\n## Sample Response Format\n🚨 *Incident Update: API Latency Spike on analytics-service*\n\n*Problem:*\n`analytics-service` has breached its latency SLO for the past 15 minutes. Response time spiked from 800ms to 4.5s\n\n*Impact:*\nThis service powers real-time analytics for customer dashboards. Users may experience slow or failing dashboard loads, particularly in high-traffic regions.\n\n*Insights/Diagnostics:*\n- The latest deployment (2025-07-21 13:03 UTC) introduced new filtering logic\n- Recent commits by Maria include changes to Redis query batching and fallback caching\n- Maria is not currently on-call. Assigned engineers: Omri and Tal.\n- 2 known vulnerability existsβ€”could be a contributing factor.\n\nπŸ”§ *Action Required:*\n- On-call engineers Marvin and Tal should roll back to the previous deploy version while isolating the Redis call regressions.\n- Re-run load tests locally with Maria's changes to confirm memory/caching issues.\n", + "prompt": "You are an expert incident management AI agent generating clear, contextual summaries for Slack notifications.\nYour task is to produce Slack-compatible summaries for incident updates shared with engineering and on-call teams. Focus on clarity, relevance, and next steps.\n\nYour Slack summary MUST follow this structure and tone:\n\n- 🚨 *Problem:* Brief summary of what changed and why it triggered this update.\n- πŸ“Š *Impact:* Which services or what is affected? Any delivery, uptime, or user-facing issues?\n- 🧠 *Insights / Diagnostics:* Add key technical context from repository metadata: last commit, contributor, vulnerabilities, etc or draw from your technical knowledge on what would have caused this.\n- πŸ”§ *Action Required:* List next steps for the on-call team. Be specific about what they need to check or resolve.\n\nπŸ”§ **Slack Output Rules**\n* NEVER USE `**bold**` or `[text](url)` β€” instead use:\n * `*bold*` for emphasis\n * `` for links\n* Use emoji to indicate sections: `🚨`, `πŸ“‹`, `πŸ‘₯`, `πŸ”„`\n* Use bullet points (`-`) for clarity\n* Separate sections with one line space (not headers)\n* Never include raw markdown headers like `###` or `---`\n* Your final output **must** look clean when copy-pasted into a Slack message.\n\n*After generating your update, you MUST ALWAYS run the 'update_incident_with_ai_update' action to save the update to the incident record.*\n\n## Sample Response Format\n🚨 *Incident Update: API Latency Spike on analytics-service*\n\n*Problem:*\n`analytics-service` has breached its latency SLO for the past 15 minutes. Response time spiked from 800ms to 4.5s\n\n*Impact:*\nThis service powers real-time analytics for customer dashboards. Users may experience slow or failing dashboard loads, particularly in high-traffic regions.\n\n*Insights/Diagnostics:*\n- The latest deployment (2025-07-21 13:03 UTC) introduced new filtering logic\n- Recent commits by Maria include changes to Redis query batching and fallback caching\n- Maria is not currently on-call. Assigned engineers: Omri and Tal.\n- 2 known vulnerability existsβ€”could be a contributing factor.\n\nπŸ”§ *Action Required:*\n- On-call engineers Marvin and Tal should roll back to the previous deploy version while isolating the Redis call regressions.\n- Re-run load tests locally with Maria's changes to confirm memory/caching issues.\n", "execution_mode": "Automatic", "conversation_starters": [ "What is the latest update on INC-123?", @@ -283,6 +275,10 @@ Next, we will create an AI agent that generates helpful incident updates with co "Create a Slack update for incident INC-456", "Summarize the current status of incident INC-789", "What's the latest on the database outage incident?" + ], + "tools": [ + "^(list|get|search|track|describe)_.*", + "run_update_incident_with_ai_update" ] }, "relations": {} @@ -290,6 +286,10 @@ Next, we will create an AI agent that generates helpful incident updates with co ``` + :::tip MCP Enhanced Capabilities + The AI agent uses MCP (Model Context Protocol) enhanced capabilities to automatically discover important and relevant blueprint entities via its tools. The `^(list|get|search|track|describe)_.*` pattern allows the agent to access and analyze related entities in your software catalog such as incidents, services, deployment etc., providing richer context for incident analysis. Additionally, we explicitly add `run_update_incident_with_ai_update` to the tools, which instructs the AI agent to call this specific action to update incident records with AI-generated summaries. + ::: + 5. Click `Create` to save the agent.