debugging-errors

Debug intermittent production errors in distributed systems by gathering logs, using correlation IDs for tracing, and applying retry or backoff patterns. A structured workflow guides evidence collection, error classification, and root-cause isolation to resolve incidents fast.

Diagnose slow responses and performance issues during an incident using a systematic debugging checklist. It directs you to gather evidence, classify the error type, isolate the failing component, identify the root cause, and verify the remediation.

Fix connection pool exhaustion and async event-loop issues by applying targeted patterns for asynchronous environments. The skill provides specific tips to identify missing await calls, resolve event-loop blocking, and manage resource limits.

You can use a structured checklist for resolving database and async runtime exceptions. The workflow covers evidence gathering, error classification tables mapping symptoms to first-check actions, and remediation patterns for logging and retries.

Error classification tables are needed for resolving production incidents because they map observed symptoms directly to likely categories and first-check actions. This eliminates manual guesswork and accelerates root-cause identification.

Systematic debugging for production runtime errors requires existing log data to function effectively. It provides checklists and remediation patterns for known distributed and async scenarios, but may be limited by incomplete logging or novel, unclassified exceptions.