Golang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for production monitoring, setting up metrics or alerting, adding OpenTelemetry tracing, correlating logs with traces, migrating legacy loggers (zap/logrus/zerolog) to slog, adding observability to new features, or implementing GDPR/CCPA-compliant tracking with Customer Data Platforms (CDP). Not for temporary deep-dive performance investigation (→ See `samber/cc-skills-golang@golang-benchmark` and `samber/cc-skills-golang@golang-performance` skills).
80
92%
Does it follow best practices?
Impact
100%
1.25xAverage score across 1 eval scenario
Passed
No findings from the security scan
OpenTelemetry HTTP client instrumentation
otelhttp transport
0%
100%
Context on HTTP requests
100%
100%
Span per gateway call
100%
100%
Span names are descriptive
100%
100%
No response body as span attribute
100%
100%
Error: RecordError called
100%
100%
Error: SetStatus called
100%
100%
Span ended
100%
100%
Context propagated in service layer
100%
100%
No request body as span attribute
100%
100%
4158351
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.