dt-proc-critical-incident

Guides systematic critical incident investigation from triage through root cause identification.

Updated Dec 12, 2025
One-click install
npx skills add https://github.com/ricardojjulia/ESACompanion --skill dt-proc-critical-incident-ricardojjulia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dt-proc-critical-incident
Source: https://github.com/ricardojjulia/ESACompanion/tree/main/.github/skills/dt-proc-critical-incident
Command: npx skills add https://github.com/ricardojjulia/ESACompanion --skill dt-proc-critical-incident-ricardojjulia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Responding to critical production incidents without a structured process leads to missed context, wasted queries on expired telemetry, and premature conclusions. This Skill enforces a disciplined incident response workflow that verifies data availability, validates findings against the incident description, and keeps customer impact front and center. ## Core Features & Use Cases - Pre-flight Incident Checklist: Confirms incident ID, reporter, description, and a complete timestamp (date, time, timezone) before any investigation begins, with data-retention guidance based on incident age. - Initial Assessment Workflow: Identifies affected components via health checks, validates findings against the incident description, and determines customer impact. - Health Check Procedures: Component-level and global cross-system health analysis using dashboards and knowledge base documents. - Incident Status Updates: Generates delta reports comparing current health against previous assessments to show whether the situation is improving or worsening. - Use Case: An on-call engineer receives incident CI-326 reporting checkout failures at 2026-03-05 14:30 UTC. The Skill walks them through the checklist, runs component health checks for the affected services, confirms customer impact, and produces a summary for stakeholders. ## Quick Start Investigate critical incident CI-326 that started at 2026-03-05 14:30 UTC affecting the checkout service and give me an initial assessment.

Frequently Asked Questions about dt-proc-critical-incident

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I investigate a critical production incident step by step?▼

Start with the incident response checklist to confirm the incident ID, reporter, description, and full timestamp with timezone. Then run the initial assessment workflow, which performs health checks on affected components, validates findings against the incident description, and determines customer impact.

How to check the health of a specific system component in Dynatrace?▼

Use the component health check workflow with the component name and a complete timestamp. It searches the knowledge base for health-related documents, analyzes relevant dashboards and health tiles, and verifies findings against a larger baseline timeframe.

Can I investigate incidents that happened more than 7 days ago?▼

Incidents older than 7 days are likely outside telemetry retention for most signal types. The workflow warns you and pivots to available artifacts such as dashboards, screenshots, existing documentation, and incident reports instead of live queries.

Why does my incident query return no data?▼

Empty results usually mean the data is outside the retention window, the entity name is wrong, or the time range is incorrect. Run a quick availability check like fetch logs filtered to the incident time with limit 1 before deeper investigation.

When should I escalate an incident instead of continuing to investigate?▼

Escalate when customer impact is confirmed and growing, root cause is not identifiable after initial assessment, multiple independent systems are affected, or the incident exceeds your access or expertise. Include current findings, ruled-out causes, timeframe, and confirmed impact.