devops-troubleshooter

Analyze logs, traces, and metrics to identify root causes of production incidents.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/chicanoandres702/SentientAIBrowser --skill devops-troubleshooter-chicanoandres702
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devops-troubleshooter
Source: https://github.com/chicanoandres702/SentientAIBrowser/tree/main/.agents/workflows/devops-troubleshooter
Command: npx skills add https://github.com/chicanoandres702/SentientAIBrowser --skill devops-troubleshooter-chicanoandres702

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces mean-time-to-recovery by guiding structured triage, log analysis, and tracing to quickly identify root causes in production outages.

Core Features & Use Cases

  • Rapid triage: Quickly collate logs, metrics, and traces to pinpoint outages.
  • Root-cause analysis: Systematically reason about failure points and propose fixes.
  • Postmortems & automation: Document learnings and suggest runbooks to prevent recurrence.

Quick Start

Analyze the latest incident data (logs, traces, metrics) to identify top three root causes and craft an immediate remediation plan.

Frequently Asked Questions about devops-troubleshooter

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

FAQPage Schema
How do I troubleshoot Kubernetes production incidents by analyzing logs and traces?

Root-cause analysis for distributed systems systematically examines logs, metrics, and traces to pinpoint failure points during an outage. It applies structured triage to identify exact causes and craft remediation plans for cloud-native applications.

What is the best way to perform rapid triage during a distributed systems outage?

Rapid triage during a distributed systems outage involves quickly collating observability data like logs, traces, and metrics. This process pinpoints the exact failure points in cloud-native applications and proposes immediate remediation steps.

Does this incident response approach work with cloud-native applications and Kubernetes environments?

Yes, this incident response approach supports Kubernetes, cloud-native applications, and distributed systems. It analyzes logs, traces, and metrics from these environments to identify root causes during live debugging and postmortems.

How do I create postmortems and runbooks after a production incident?

You create postmortems and runbooks after a production incident by documenting learnings from your root-cause analysis. This process suggests automation and runbooks to prevent recurrence and reduce future mean-time-to-recovery.

What are the limitations of using observability data for live debugging in distributed systems?

A limitation of using observability data for live debugging is the reliance on complete logs, traces, and metrics. Without integrated monitoring tools, identifying root causes in distributed systems becomes difficult.