golang-observability

Instrument Go services with logs, metrics, traces, and profiling.

5|1|Updated Apr 14, 2026

Search Tags:#logging #go #observability #tracing #prometheus #opentelemetry #pprof

Ready to run

npx skills add https://github.com/omarluq/og-template --skill golang-observability-omarluq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: golang-observability
Source: https://github.com/omarluq/og-template/tree/main/.agents/skills/golang-observability
Command: npx skills add https://github.com/omarluq/og-template --skill golang-observability-omarluq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Golang observability ensures you can understand production behavior through structured logs, metrics, traces, profiling, and Real User Monitoring integration.

Core Features & Use Cases

Instrumentation patterns for logs, metrics, tracing, and profiling in Go services.
OpenTelemetry integration, slog-based logging, pprof/Pyroscope profiling, server-side RUM, alerting and dashboards.
Migration guidance for replacing zap/logrus/zerolog with slog, and ensuring observability is added before features are considered done.

Quick Start

Instrument a Go service by adding signals (logs, metrics, traces, profiling) per the guide and verify that traces appear in Tempo, logs in Loki, and metrics in Prometheus.

Frequently Asked Questions about golang-observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up OpenTelemetry tracing and Prometheus metrics in a Go service?▼

Yes, the Skill provides migration guidance for replacing zap, logrus, or zerolog with slog. This ensures your structured logging aligns with modern Go observability standards before features are considered done.

Can I use pprof and Pyroscope for Go profiling in production?▼

Real User Monitoring integration involves server-side RUM data collection with privacy controls. This captures frontend performance metrics alongside backend traces to provide full end-to-end observability for Go services.

What is the best way to add end-to-end observability to existing Go microservices?▼

You verify observability by checking that traces appear in Tempo, logs in Loki, and metrics in Prometheus. This validation confirms your Go service instrumentation correctly exports telemetry data to the monitoring backends.

Does Go observability require structured logging with slog?▼

Observability should be added before features are considered done, applying instrumentation to service methods, database queries, and external API calls. This ensures production behavior is fully understood through logs, metrics, and traces.