What problem does it solve?
It solves the risk of shipping Go features that are not measurable in production, so you can’t diagnose latency, errors, saturation, or user experience issues quickly.
Core Features & Use Cases
- Structured logging with
log/slog: production-ready JSON logs, correct level usage, and trace correlation via *Context logging.
- Prometheus metrics: metric type selection (Counter/Gauge/Histogram/Summary), low-cardinality labels, latency histograms with percentile querying, and PromQL-as-comments for discoverability.
- OpenTelemetry tracing: early TracerProvider setup, spans for meaningful operations, context propagation across boundaries, and correct error recording on spans.
- Profiling (pprof + continuous profiling): secure pprof exposure patterns and environment-variable toggling, plus Pyroscope continuous profiling guidance.
- Server-side RUM event tracking: backend event capture, identity rules using immutable
user_id, consent-aware tracking, and privacy compliance considerations (GDPR/CCPA).
- Alerting and dashboards: Golden signals coverage (latency/traffic/errors/saturation), multi-window burn-rate SLO alerts, runtime alerts, and Grafana dashboard alignment.
Quick Start
Add observability to your Go service by instrumenting logs, metrics, traces, profiling, and (when needed) server-side RUM with the skill’s production-grade rules and verification checklist.