observability-troubleshooting

Correlates logs, traces, metrics, and dashboards to identify root causes of incidents.

1|Updated Apr 2, 2026

Search Tags:#troubleshooting #logs #metrics #observability #traces #root-cause #incident-analysis

Ready to run

npx skills add https://github.com/thomassloboda/ai-stuff --skill observability-troubleshooting-thomassloboda

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability-troubleshooting
Source: https://github.com/thomassloboda/ai-stuff/tree/main/skills/observability-troubleshooting
Command: npx skills add https://github.com/thomassloboda/ai-stuff --skill observability-troubleshooting-thomassloboda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps you investigate incidents and service issues by correlating logs, traces, metrics, dashboards, and other observability signals to quickly narrow down the likely cause.

Core Features & Use Cases

Correlate signals across sources (logs, traces, metrics) to form a unified incident view.
Identify affected services, routes, or dependencies and estimate blast radius.
Provide structured guidance for next diagnostic steps and potential owners.

Quick Start

Analyze the latest incident signals and provide a concise incident summary with proposed next checks.

Frequently Asked Questions about observability-troubleshooting

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

FAQPage Schema

How do I correlate logs, traces, and metrics to find the root cause of an incident?▼

Incident analysis correlates logs, traces, and metrics to form a unified view of the issue. This process narrows down affected services, dependencies, and the blast radius to identify the root cause.

What is the best way to investigate cross-service latency regressions and error spikes?▼

Investigating latency regressions and error spikes requires correlating dashboards and observability signals across services. This approach identifies affected routes and dependencies, providing structured hypotheses and next diagnostic checks.

Can I use observability signals to estimate the blast radius of a throughput change?▼

Yes, you can estimate the blast radius of a throughput change by correlating observability signals across monitored environments. This identifies affected services and dependencies to assess the scope of the incident.

How do I get structured guidance for next diagnostic steps during a service outage?▼

To get structured guidance during a service outage, you analyze the latest incident signals to produce a summary. This output includes observations, hypotheses, evidence, next checks, and potential ownership assignments.

Does this approach work for narrowing down root causes across monitored environments?▼

Yes, this approach works for narrowing down root causes across monitored environments. It applies to cross-service incidents, latency regressions, error spikes, and throughput changes by correlating logs, traces, and metrics.