What problem does it solve? Production features often ship without telemetry, so when incidents occur 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 the outside. ## Core Features & Use Cases - Structured Logging: Emits JSON log events with stable event names, correlation IDs, entry-point attribution, and consistent log levels while keeping secrets and PII out of logs. - Metrics and Tracing: Applies RED/USE metrics with bounded label cardinality and histogram percentiles, plus OpenTelemetry distributed tracing with context propagation across services. - Symptom-Based Alerting: Defines actionable alerts tied to user-facing symptoms with runbook links, thresholds, and two severity tiers, then verifies telemetry by triggering real failures. - Use Case: When adding a payment retry flow, use this Skill to define the on-call questions first, then add structured payment_failed log events, a latency histogram for the provider, a trace span around the charge call, and an alert on elevated error rate. ## Quick Start Use the observability-and-instrumentation skill to add structured logging, RED metrics, tracing, and an alert to my new checkout endpoint.
