incident-investigation

To correlate PagerDuty incidents with Jira tickets and ArgoCD deployments, this Skill orchestrates multiple agents to gather incident data, tickets, and deployment history into a unified root cause analysis timeline.

Building an incident timeline during an active outage involves fetching PagerDuty incidents, Jira tickets, and ArgoCD deployment history to construct a complete narrative of events and surface cross-system relationships.

You can use this incident investigation approach for post-mortem analysis by correlating past PagerDuty alerts with Jira tickets and ArgoCD deployments to surface cross-system relationships and identify the blast radius.

This root cause analysis workflow requires no external dependencies, as it orchestrates multiple agents natively to query PagerDuty, Jira, and ArgoCD directly without needing additional components.

Correlating alerts with ArgoCD deployment history identifies blast radius by surfacing cross-system relationships between recent code changes and affected components, linking deployment events directly to incident triggers.