skills.rest
claushaas
claushaasCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

observability-troubleshooting

Guide instrumentation of logs, metrics, traces, and alerts for production incidents.

Updated Aug 27, 2026
Search Tags:#troubleshooting#logs#metrics#observability#traces#SLOs
One-click install
npx skills add https://github.com/claushaas/claus-haas-ai-stuff --skill observability-troubleshooting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: observability-troubleshooting
Source: https://github.com/claushaas/claus-haas-ai-stuff/tree/main/skills/observability-troubleshooting
Command: npx skills add https://github.com/claushaas/claus-haas-ai-stuff --skill observability-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams gain visibility into complex systems by guiding the addition or improvement of logs, metrics, traces, and alerts to diagnose production incidents or performance issues.

Core Features & Use Cases

  • Structured visibility: defines signals and how to surface them for fast root-cause analysis.
  • SLO definition & alerting: supports defining service level objectives and alerting to monitor health.
  • Instrumenting critical paths: guides instrumentation points in high-impact flows to prevent blind spots.
  • Use cases include latency troubleshooting, incident postmortems, capacity planning with telemetry.

Quick Start

Audit your current telemetry signals for your top 3 transactions and propose missing instrumentation to improve detection and diagnosis.

Frequently Asked Questions about observability-troubleshooting

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

FAQPage Schema
How do I improve observability for faster incident resolution?▼

Improve observability by auditing existing telemetry signals for critical user journeys and proposing missing instrumentation across logs, metrics, and traces. This structured visibility surfaces issues quickly to speed up root-cause analysis during incidents.

How do I instrument critical paths to prevent observability blind spots?▼

Instrument critical paths by identifying high-impact flows in your top transactions and adding targeted telemetry. This guided instrumentation prevents blind spots and ensures detection of latency issues with minimal performance impact.

What is the best way to troubleshoot latency issues using traces and metrics?▼

Troubleshoot latency issues by analyzing existing traces and metrics across critical user journeys to identify bottlenecks. Guided instrumentation of missing telemetry signals improves diagnosis of performance degradation.

Can I use this for capacity planning with telemetry data?▼

Yes, you can use telemetry data for capacity planning. By analyzing metrics and traces from critical system paths, you can forecast resource needs and identify performance bottlenecks before they impact production stability.

Why do I need structured visibility for incident postmortems?▼

Structured visibility is needed for incident postmortems because it defines how telemetry signals are surfaced, allowing teams to accurately diagnose production incidents and understand root causes without blind spots.

Related Skills

Explore More Software Engineering Skills→
HemantSudarshanHemantSudarshan

observability-engineer

Define production observability signals, instrumentation, dashboards, and alerting for microservices.

Community
Advanced
TheBushidoCollectiveTheBushidoCollective
187

sre-incident-response

Manage production incidents across detection, triage, mitigation, and postmortem workflows.

Official
Intermediate
Prathmesh2000Prathmesh2000
1

observability-engineer

Instrument JSON logs, OpenTelemetry traces, and metrics for cloud-native observability.

Community
Advanced
PriyanshKuniyalPriyanshKuniyal

slo-implementation

Automate SLI and SLO definition, tracking, and alerting with Prometheus and Grafana.

Community
Advanced