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, mandatory correlation IDs, entry-point attribution, and consistent log levels while keeping secrets and PII out of log pipelines. - Metrics and Tracing: Applies RED (Rate, Errors, Duration) and USE (Utilization, Saturation, Errors) methods with bounded label cardinality, histogram-based latency percentiles, and OpenTelemetry distributed tracing with context propagation. - Alerting and Runbooks: Defines symptom-based alerts with page/ticket severities, thresholds, durations, and linked runbooks, plus a verification step that test-fires alerts and validates telemetry output. - Use Case: When adding a payment retry flow, you define the on-call questions first, then add a payment_failed structured log event, a latency histogram for the provider, an OpenTelemetry span around the charge call, 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.
