devops-troubleshooter

Diagnose production outages through log analysis and distributed tracing.

10|2|Updated Mar 10, 2026

Search Tags:#devops #performance #debugging #troubleshooting #kubernetes #observability #incident response

Ready to run

npx skills add https://github.com/bugrabilge/bilge-development-kit --skill devops-troubleshooter-bugrabilge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: devops-troubleshooter
Source: https://github.com/bugrabilge/bilge-development-kit/tree/main/skills/devops-troubleshooter
Command: npx skills add https://github.com/bugrabilge/bilge-development-kit --skill devops-troubleshooter-bugrabilge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides expert assistance for rapidly resolving DevOps incidents, debugging complex system issues, and improving overall system reliability and performance.

Core Features & Use Cases

Incident Response: Quickly diagnose and resolve production outages and system failures.
Advanced Debugging: Deep dive into logs, traces, and metrics to find root causes.
Observability Mastery: Leverage expertise in tools like ELK, Prometheus, Grafana, and distributed tracing.
Use Case: When a critical service experiences intermittent errors, this Skill can analyze logs and traces across microservices to pinpoint the exact source of the problem and suggest a fix.

Quick Start

Debug high memory usage in Kubernetes pods causing frequent OOMKills and restarts.

Frequently Asked Questions about devops-troubleshooter

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

FAQPage Schema

How do I debug high memory usage in Kubernetes pods causing frequent OOMKills?▼

Debug Kubernetes OOMKills by analyzing pod memory metrics and container resource limits to identify memory leaks. This Skill helps diagnose high memory usage causing restarts by examining pod logs, tracing resource exhaustion, and suggesting configuration fixes to prevent out-of-memory terminations.

What is the best way to analyze distributed tracing for intermittent microservices errors?▼

Analyze distributed tracing for microservices by correlating spans across service boundaries to pinpoint exact failure sources. This Skill specializes in tracing intermittent errors across microservices, leveraging observability platforms to identify latency bottlenecks and root causes in production environments.

How do I perform root cause analysis for a production outage using Prometheus and Grafana?▼

Perform root cause analysis for production outages by querying Prometheus metrics and visualizing anomaly patterns in Grafana dashboards. This Skill masters observability platforms to correlate system failures with metric spikes, enabling rapid identification of the underlying issue triggering the outage.

Can I use this for incident response and log analysis with the ELK stack?▼

Yes, you can use this for incident response and log analysis with the ELK stack. It provides expert DevOps troubleshooting by leveraging expertise in tools like ELK, quickly diagnosing and resolving production outages by deep diving into logs to find root causes.

Why does my service experience performance degradation and how can I optimize it?▼

Service performance degradation often stems from resource bottlenecks or network issues, which you can optimize through performance profiling. This Skill performs advanced debugging and performance optimization by analyzing system metrics, network traffic, and application traces to resolve reliability issues.

When do I need distributed tracing versus standard log analysis for troubleshooting?▼

You need distributed tracing for troubleshooting complex microservices interactions, while standard log analysis suffices for isolated application errors. This Skill determines the appropriate observability approach by evaluating whether system failures require cross-service correlation or localized debugging.