What problem does it solve? Production features often ship without telemetry, so when something breaks you 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, mandatory correlation IDs, entry-point attribution, and consistent log levels, while keeping secrets and PII out of telemetry. - Metrics and Tracing: Applies RED/USE metrics with bounded label cardinality and histogram percentiles, plus OpenTelemetry distributed tracing with context propagation across services and queues. - Symptom-Based Alerting and Runbooks: Defines actionable alerts on user-facing symptoms with thresholds, severities, and linked runbooks, then verifies the telemetry itself by inducing failures in staging. - 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, RED metrics on the provider calls, trace spans around charging, and an alert on error rate with a runbook link. ## Quick Start Use the observability-and-instrumentation skill to add structured logging, RED metrics, tracing, and an alert with a runbook to my new checkout endpoint.
