What problem does it solve? Production features often ship without telemetry, leaving teams blind when incidents occur and unable to answer what the system is doing or why. This Skill guides you to instrument code alongside development so failures are diagnosable from logs, metrics, and traces instead of guesswork. ## Core Features & Use Cases - Structured Logging: Enforces JSON log events with stable event names, correlation IDs, entry-point attribution, and consistent log levels, while blocking secrets and PII from telemetry. - Metrics and Tracing: Applies RED/USE metric patterns with bounded label cardinality and histogram percentiles, plus OpenTelemetry-based distributed tracing with context propagation. - Symptom-Based Alerting: Designs actionable alerts tied to user-facing symptoms with runbook links, and verifies telemetry by inducing failures in staging. - Use Case: When adding a payment retry flow with a queue and an external provider, use this Skill to define on-call questions, emit structured payment_failed events, add RED metrics for the provider, and create a symptom-based alert before shipping. ## Quick Start Use the observability-and-instrumentation skill to add structured logging, RED metrics, and OpenTelemetry tracing to my new checkout endpoint before it ships.
