What problem does it solve? Go services shipped without observability are black boxes in production — you cannot diagnose latency spikes, error bursts, or resource leaks without logs, metrics, traces, and profiles wired together. This Skill guides the instrumentation of Go services across all five observability signals so every feature is monitorable before it ships. ## Core Features & Use Cases - Structured logging with slog: JSON handlers for production, context-aware log variants for trace correlation, and incremental migration from zap, logrus, or zerolog using bridge handlers. - Prometheus metrics and alerting: correct use of Counters, Gauges, and Histograms, naming conventions, low-cardinality label discipline, PromQL-as-comments convention, multi-window burn-rate SLO alerts, and Go runtime alerts for goroutine leaks and GC pressure. - OpenTelemetry tracing and profiling: span placement on service methods, DB queries, and external calls, context propagation, exemplars linking metrics to traces, and pprof/Pyroscope profiling toggled via environment variables. - Use Case: When adding a new HTTP endpoint to a Go service, use this Skill to declare latency and error metrics with PromQL comments, add spans with error recording, emit structured context-aware logs, and wire the corresponding Grafana dashboard and alert rules. ## Quick Start Ask the agent to add production observability instrumentation to your Go service, covering slog logging, Prometheus metrics, and OpenTelemetry tracing for a specific handler or package.
