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 golang-benchmark and golang-performance skills).
87
86%
Does it follow best practices?
Impact
91%
1.10xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
New service observability instrumentation
JSON log handler
100%
0%
LevelInfo in production
100%
0%
Context log variants
100%
100%
No PII in logs
100%
100%
Error log-or-return
0%
100%
Histogram for latency
100%
100%
PromQL comments on metrics
0%
100%
Bounded metric labels
100%
100%
Counter _total suffix
100%
100%
TracerProvider setup
100%
100%
Spans on service methods
100%
100%
DB calls use QueryContext/ExecContext
100%
100%
otelhttp transport for HTTP client
0%
100%
Span error recording
100%
100%
Metric base units
100%
100%
Prometheus alerting rules configuration
rate() not irate()
100%
100%
for: on all non-binary alerts
100%
100%
Two severity levels only
100%
100%
Critical for: duration
66%
66%
Warning for: duration
33%
33%
Latency alert (golden signal)
100%
100%
Traffic alert (golden signal)
100%
100%
Error rate alert (golden signal)
100%
100%
Saturation alert (golden signal)
100%
100%
Multi-window SLO alerting
100%
100%
Go runtime goroutine alert
100%
100%
Go runtime GC alert
100%
100%
Go runtime memory alert
100%
100%
Infrastructure rules sourced externally
0%
100%
Predictive saturation alert
0%
0%
GDPR-compliant server-side analytics integration
user_id as identity key (PostHog)
100%
100%
user_id as identity key (Segment)
100%
100%
Consent check before PostHog
100%
100%
Consent check before Segment
100%
100%
Data deletion endpoint
100%
100%
Deletion propagates to analytics
75%
100%
Deletion propagates to CDP
25%
100%
Data export endpoint
100%
100%
No PII in analytics events
100%
100%
No PII in log calls
100%
100%
Both clients initialized
100%
100%
GDPR compliance documented
100%
100%
b88f91d
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.