What problem does it solve?
Teams and services that lack reliable monitoring, structured logs, and distributed traces struggle to detect, diagnose, and measure incidents; this Skill implements end-to-end observability so engineering teams can rapidly find and fix production issues and verify reliability improvements.
Core Features & Use Cases
- Metrics & Instrumentation: Define RED/USE and business metrics, recommend low-cardinality Prometheus metrics and cardinality limits.
- Structured Logging: Enforce JSON logs, include request_id and trace_id, and exclude PII and secrets.
- Distributed Tracing: Auto-instrument with OpenTelemetry, propagate trace IDs, and recommend sampling strategies.
- SLOs, Alerts & Dashboards: Create SLIs/SLOs, error-budget aware alerts with proper
for durations, and dashboards covering the Four Golden Signals.
- Use Case: Add monitoring and alerting to an API service to detect p99 latency regressions, capture traces for slow requests, and notify on error budget burn.
Quick Start
Add Prometheus metrics, structured JSON logs with request_id, and OpenTelemetry traces, then define an SLO and a critical alert for high error rate.