incident-analyzing

Root cause analysis in distributed systems requires structured causal hypothesis testing against logs, traces, and system behavior to identify the exact failure origin. This Skill applies that methodology to pinpoint whether failures stem from service overloads, deployments, or dependencies.

Stack trace analysis identifies error patterns and their likely origins in code by reading topology and failure pattern references. It isolates specific code segments causing exceptions to determine if issues stem from database overloads, recent deployments, or downstream dependency failures.

Impact assessment quantifies the blast radius of an active incident by evaluating user impact and revenue path disruption. It maps the confirmed causal chain to determine exactly which downstream services and users are affected by the identified failure origin.

Root cause analysis applies structured hypothesis testing to identify failure origins across services, CI pipelines, and local environments. It reads topology and failure pattern references to systematically trace the causal chain regardless of where the active incident originates.

Troubleshooting a critical service down requires analyzing error logs and system metrics to pinpoint whether the issue stems from a database overload, a recent deployment, or a downstream dependency failure. Structured hypothesis testing confirms the causal chain across the distributed system topology.