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 incidents become queries instead of archaeology. ## Core Features & Use Cases - Question-driven instrumentation: Define the on-call questions first, then map structured logs, RED/USE metrics, and OpenTelemetry traces to each question. - Structured logging with correlation IDs: Emit JSON log events with stable names and request IDs propagated across services, while keeping secrets and PII out of telemetry. - Symptom-based alerting: Create actionable alerts on user-facing symptoms with runbook links, and verify telemetry by triggering failures in staging. - Use Case: When adding a payment retry flow, use this Skill to add a payment_failed structured log event, a latency histogram for the provider call, a trace span around the charge operation, and an alert on elevated error rate. ## Quick Start Instrument my new checkout endpoint with structured logging, RED metrics, and an OpenTelemetry trace, then define the alerts an on-call engineer would need.
