investigating-pagerduty-incidents_skill

Overview

This skill generates a concise weekly PagerDuty incident report for the Music Mission MIQ team covering the fan-audio and fusion services. It inspects PagerDuty incidents and GCP logs, extracts root causes for fan-audio errors, and produces a Word document ready to paste into Slack with actionable findings and debugging links.

How this skill works

The workflow fetches incidents from the past week (resolved and open) via the pd CLI, queries GCP logs around incident timestamps for fan-audio to identify error patterns, groups incidents by root cause, and fills a python-docx template to produce pagerduty-report-YYYY-MM-DD.docx. Representative alert links are attached for each root cause so recipients can jump straight to investigations.

When to use it

• Produce a weekly summary of PagerDuty incidents for fan-audio and fusion
• Investigate root causes of fan-audio errors using GCP logs
• Create a single-page, actionable report for Slack distribution
• Share representative debugging links rather than full incident lists

Best practices

• Group incidents by root cause; avoid listing each incident
• Filter GCP logs to exclude UserWarnings and noisy messages
• Query a 1-hour window around each incident timestamp for concrete errors
• Include 2–4 concrete action items and one representative link per root cause
• Keep the document to one page; focus on next steps and impact

Example use cases

• Weekly team report: quantify incidents and summarize top root causes for the week
• Root cause analysis for recurring fan-audio DEADLINE_EXCEEDED errors with representative log links
• Emergency follow-up: create a short, actionable doc for on-call handoff
• Provide stakeholders with an at-a-glance list of action items and debugging URLs