golang-observability

Automate Go observability instrumentation for logs, metrics, traces, profiling, and RUM.

7|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Harmeet10000/skills --skill golang-observability-harmeet10000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golang-observability
Source: https://github.com/Harmeet10000/skills/tree/main/skills/backend/Golang/golang-observability
Command: npx skills add https://github.com/Harmeet10000/skills --skill golang-observability-harmeet10000

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Go services often operate in complex distributed environments where logs, metrics, and traces are siloed, making it hard to diagnose issues quickly.

Core Features & Use Cases

  • Structured logging with slog and OpenTelemetry bridging to correlate logs with traces.
  • Prometheus metrics with histograms, dashboards, and alerting patterns for SLOs.
  • Distributed tracing setup and best practices for context propagation.
  • Profiling strategies (pprof, Pyroscope) with production-safe toggles.
  • Real User Monitoring (RUM) integration and GDPR/CCPA considerations.

Quick Start

Enable the full observability stack in your Go services by wiring logs, metrics, traces, profiling, and RUM with the recommended defaults.

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 end-to-end observability in Go services with OpenTelemetry and Prometheus?

Structured logging with slog bridges to OpenTelemetry traces by correlating log entries with trace identifiers, ensuring logs and traces are linked across distributed Go services. This cross-service correlation makes it easier to diagnose issues in complex environments quickly.

What's the best way to correlate Go slog logs with distributed traces?

Structured logging with slog bridges to OpenTelemetry traces by correlating log entries with trace identifiers, ensuring logs and traces are linked across distributed Go services. This cross-service correlation makes it easier to diagnose issues in complex environments quickly.

Can I enable production-safe profiling in Go services using pprof?

Profiling strategies for Go services include pprof and Pyroscope with production-safe toggles, allowing you to capture performance data without impacting live service stability. These profiling tools help diagnose CPU and memory issues in production environments.

How do I implement Prometheus metrics and SLO alerting patterns in Go?

Prometheus metrics in Go are implemented using histograms to track latency and request distributions, combined with dashboard and alerting patterns for SLOs. This setup provides actionable visibility into service performance and reliability for production-grade environments.

Does Go observability instrumentation support GDPR and CCPA compliant tracking?

GDPR and CCPA compliant tracking is supported through Real User Monitoring (RUM) integration considerations built into the observability setup. This ensures end-to-end signal visibility respects user privacy regulations across production Go services.

Why are my Go service logs, metrics, and traces siloed and hard to diagnose?

Go service logs, metrics, and traces become siloed when they operate in complex distributed environments without unified instrumentation. Automating observability across signals with OpenTelemetry context propagation resolves this by correlating data end-to-end.