observability

Correlate logs, traces, and errors to triage production incidents.

6|2|Updated Jul 8, 2012

Search Tags:#monitoring #logs #observability #triage #traces #root-cause-analysis #incident-management

Ready to run

npx skills add https://github.com/athal7/dotfiles --skill observability-athal7

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability
Source: https://github.com/athal7/dotfiles/tree/main/skills/observability
Command: npx skills add https://github.com/athal7/dotfiles --skill observability-athal7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate production problems by correlating logs, traces, and errors to triage incidents and know when to escalate.

Core Features & Use Cases

Triage incidents by starting with symptom hypotheses, narrowing time windows, and identifying scope.
Correlate signals across logs, traces, and errors using trace.id to assemble end-to-end context.
Escalate to on-call teams with clear thresholds and escalation criteria.

Quick Start

Query traces and logs for the incident window and correlate signals to identify the root cause.

Frequently Asked Questions about observability

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

FAQPage Schema

How do I triage production incidents by correlating logs and traces?▼

Triage production incidents by starting with symptom hypotheses, narrowing time windows, and identifying scope, then correlating logs and traces to pinpoint the root cause. This structured process helps on-call engineers assemble end-to-end context for diagnosis.

What is root cause analysis in observability and how does trace.id linkage work?▼

Root cause analysis in observability identifies the origin of production issues by correlating signals across logs, traces, and errors. Using trace.id linkage, you connect related telemetry data to assemble end-to-end context for accurate incident diagnosis.

How do I know when to escalate an incident to on-call teams?▼

Escalate an incident to on-call teams by evaluating clear thresholds and escalation criteria during triage. After correlating logs and traces to understand the scope, use these predefined criteria to determine if the issue requires immediate escalation.

Can I diagnose production issues across services and endpoints using logs and traces?▼

Yes, you can diagnose production issues across services and endpoints by querying traces and logs for the incident window. Correlating these signals using trace.id assembles the necessary context to identify the root cause across affected services.

Do I need access to logs, traces, and errors with trace.id linkage for incident triage?▼

Yes, incident triage requires access to logs, traces, and errors with trace.id linkage. This access is necessary to correlate signals across services and endpoints, providing the structured signal hierarchy needed for effective root cause analysis.