golang-observability

Configure structured logging, metrics, tracing, and profiling for Go services.

Updated May 30, 2026
One-click install
npx skills add https://github.com/ozan-fn/mqtt-capture --skill golang-observability-ozan-fn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golang-observability
Source: https://github.com/ozan-fn/mqtt-capture/tree/main/.agents/skills/golang-observability
Command: npx skills add https://github.com/ozan-fn/mqtt-capture --skill golang-observability-ozan-fn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires go, prometheus, opentelemetry, pprof, pyroscope, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill unit provides comprehensive observability tools for Go services, addressing logging, metrics, tracing, profiling, and real-user monitoring, helping engineers gain full visibility into their applications.

Core Features & Use Cases

  • Structured Logging: Use slog for structured logging, improving log aggregation and analysis.
  • Metrics Collection: Leverage Prometheus for metrics collection, including counters, gauges, histograms, and summaries.
  • Distributed Tracing: Implement OpenTelemetry for distributed tracing across service boundaries.
  • Profiling: Use pprof and Pyroscope for continuous profiling and performance analysis.
  • Real User Monitoring (RUM): Track user experience with product analytics and session replay.
  • Use Case: When developing a new Go service, this Skill unit can be used to set up observability tools from the ground up, ensuring that metrics, logs, and traces are properly configured and correlated.

Quick Start

Use the golang-observability skill to set up structured logging for your project.

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 observability for a new Go service with logging, metrics, and tracing?

Improve Go observability by integrating slog for structured logging, Prometheus for metrics, and OpenTelemetry for distributed tracing. This configures and correlates logs, metrics, and traces from the ground up.

What is the best way to collect metrics and monitor performance in a Go application?

Leverage Prometheus for metrics collection including counters, gauges, histograms, and summaries. Combine this with pprof and Pyroscope for continuous profiling and performance analysis in Go applications.

How does distributed tracing work with OpenTelemetry across Go service boundaries?

Implement OpenTelemetry for distributed tracing to track requests across Go service boundaries. This provides visibility into production environments and helps diagnose issues across distributed systems.

Do I need Prometheus and Pyroscope to use this Go observability setup?

Yes, this Go observability setup requires Prometheus for metrics collection and Pyroscope for continuous profiling. You also need the Go runtime, OpenTelemetry, and pprof to enable full application visibility.

Can I track real user monitoring and session replay in a Go backend service?

Yes, you can track real user monitoring (RUM) in Go services by implementing product analytics and session replay. This tracks user experience alongside backend metrics, logs, and traces for full visibility.