What problem does it solve? Production features often ship without telemetry, so when something breaks, engineers cannot tell what happened from the available data. This Skill guides you to instrument code alongside the feature so production behavior is visible, queryable, and diagnosable from day one. ## 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 log output. - Metrics and Tracing: Applies RED/USE metric patterns with bounded label cardinality, histogram-based latency percentiles, and OpenTelemetry distributed tracing with context propagation. - Alerting and Runbooks: Designs symptom-based alerts with two severity tiers, actionable thresholds, and linked runbooks, plus a verification pass that test-fires alerts and validates telemetry end-to-end. - Use Case: When adding a payment retry flow with a queue and an external provider, use this Skill to define the on-call questions, add structured payment_failed events, RED metrics on the provider calls, a trace across services, and a symptom alert with a runbook before shipping. ## Quick Start Ask the AI to instrument your new production endpoint or background job with structured logging, RED metrics, tracing, and an alert with a runbook using this observability skill.
