observability-and-instrumentation

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 development so production behavior is visible, queryable, and diagnosable. ## Core Features & Use Cases - Structured Logging: Enforces JSON log events with stable event names, consistent log levels, mandatory correlation IDs, and strict rules against logging secrets or PII. - Metrics and Tracing: Applies RED/USE metric patterns with bounded label cardinality, histogram-based latency percentiles, and OpenTelemetry distributed tracing with context propagation. - Symptom-Based Alerting: Designs actionable alerts tied to user-facing symptoms with runbook links, plus a verification process that test-fires alerts and validates telemetry end-to-end. - Use Case: When adding a payment retry flow with external provider calls, use this Skill to define on-call questions, emit structured payment_failed events, add RED metrics for the provider, and create an alert on error rate with a runbook. ## Quick Start Ask the agent to instrument your new production endpoint with structured logging, RED metrics, tracing, and a symptom-based alert using this observability skill.