What problem does it solve? Production features often ship without telemetry, so when something breaks, engineers cannot tell what happened from the available data. This Skill guides you to instrument code alongside the feature so production behavior is visible and diagnosable from day one. ## Core Features & Use Cases - Structured Logging: Enforces JSON log events with stable event names, consistent log levels, and mandatory correlation/request IDs propagated across services. - Metrics and Tracing: Applies RED (Rate, Errors, Duration) and USE (Utilization, Saturation, Errors) methods with bounded label cardinality, plus OpenTelemetry-based distributed tracing with context propagation. - Symptom-Based Alerting: Designs actionable alerts tied to user-facing symptoms with runbook links, thresholds, and two severity tiers, then verifies telemetry by inducing failures in staging. - Use Case: When adding a payment retry flow with external provider calls, use this Skill to define on-call questions, emit structured payment_failed events, add latency histograms for provider calls, trace requests end-to-end, and create an alert on elevated error rates. ## Quick Start Instrument my new checkout endpoint with structured logs, RED metrics, and an OpenTelemetry trace, then define one symptom-based alert for it.
