What problem does it solve? Production features often ship without telemetry, turning every incident into guesswork. This Skill guides you to instrument code with structured logs, RED/USE metrics, distributed tracing, and symptom-based alerts so on-call engineers can answer what the system is doing and why. ## Core Features & Use Cases - Structured Logging: Enforces JSON log events with stable names, consistent levels, and mandatory correlation/request IDs, while blocking secrets and PII from log output. - Metrics and Tracing: Applies RED metrics for endpoints and dependencies, USE metrics for resources, histogram-based latency percentiles, and OpenTelemetry auto-instrumentation with context propagation. - Alerting and Verification: Designs symptom-based alerts with runbooks and two severities, plus a checklist to test-fire alerts and locate induced failures via telemetry alone. - Use Case: When adding a payment retry flow, use this Skill to define on-call questions, emit a payment_failed structured event, add provider latency histograms, and create an error-rate alert linked to a runbook. ## Quick Start Use the observability-and-instrumentation skill to add logging, metrics, tracing, and alerts to my new checkout endpoint.
