monitoring-observability

Implement OpenTelemetry traces, metrics, and logs with SLO-based alerting.

88|22|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/travisjneuman/.claude --skill monitoring-observability-travisjneuman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring-observability
Source: https://github.com/travisjneuman/.claude/tree/main/skills/monitoring-observability
Command: npx skills add https://github.com/travisjneuman/.claude --skill monitoring-observability-travisjneuman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides comprehensive solutions for understanding and troubleshooting complex software systems by implementing robust monitoring, logging, and tracing strategies.

Core Features & Use Cases

  • Observability Pillars: Integrates OpenTelemetry for traces, metrics, and structured logs.
  • Alerting: Configures SLO-based alerts to focus on user impact and reduce noise.
  • Debugging: Enables correlation across logs, traces, and metrics for efficient distributed system debugging.
  • Use Case: When a microservice is experiencing high latency, use this Skill to trace requests across services, examine structured logs for errors, and check relevant metrics to pinpoint the root cause.

Quick Start

Configure OpenTelemetry auto-instrumentation for a Node.js service by importing the provided tracing setup.

Frequently Asked Questions about monitoring-observability

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

FAQPage Schema
How do I implement distributed tracing for microservices using OpenTelemetry?

Distributed tracing with OpenTelemetry tracks requests across microservices to pinpoint latency and errors. This Skill provides instrumentation patterns to correlate traces with structured logs, enabling efficient debugging of complex distributed systems.

What is SLO-based alerting and how does it reduce monitoring noise?

SLO-based alerting focuses on user impact by triggering alerts when service level objectives are violated. This approach reduces noise by prioritizing actionable metrics over raw threshold breaches, ensuring alerts reflect actual system health.

How do I correlate structured logs with traces and metrics for debugging?

Correlating structured logs with traces and metrics involves using OpenTelemetry to inject shared context IDs across all three pillars. This allows you to examine structured logs for errors and check relevant metrics alongside distributed traces.

Can I use OpenTelemetry auto-instrumentation for a Node.js service?

Yes, OpenTelemetry supports auto-instrumentation for Node.js services. This Skill includes scripts to quickly configure tracing setup by importing the provided OpenTelemetry instrumentation patterns for immediate observability.

What are the three pillars of observability and when do I need them?

The three pillars of observability are traces, metrics, and logs. You need them when troubleshooting complex software systems, as combining these data streams provides comprehensive insights into application performance and failure points.

How do I configure health and readiness probes for microservices?

Health and readiness probes monitor microservice availability and traffic readiness. This Skill provides patterns to configure probes alongside SLO-based alerting and OpenTelemetry instrumentation to maintain system reliability.