Correlate logs, traces, and errors to triage production incidents.
npx skills add https://github.com/athal7/dotfiles --skill observability-athal7
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
Investigate production problems by correlating logs, traces, and errors to triage incidents and know when to escalate.
Query traces and logs for the incident window and correlate signals to identify the root cause.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
israel-salgadoInventory and monitor host, process, and container telemetry across environments.
claudcherejiDetect, diagnose, and resolve production incidents using observability tools.
junchenghuoDefine SLO metrics, alert thresholds, and incident review processes.
lucas-flatwhiteMonitor URLs for console errors, performance regressions, and page failures after deploy.
