go-observability

Standardize Go service logs, metrics, and traces with slog, Prometheus, and OpenTelemetry.

Updated May 2, 2026
One-click install
npx skills add https://github.com/Qunnnn/agents --skill go-observability-qunnnn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-observability
Source: https://github.com/Qunnnn/agents/tree/main/skills/go/go-observability
Command: npx skills add https://github.com/Qunnnn/agents --skill go-observability-qunnnn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps Go developers design production-ready observability systems by addressing inconsistent logging, incomplete metrics, and missing distributed tracing practices.

Core Features & Use Cases

  • Structured Logging: Guides implementation of contextual JSON logging with Go slog for searchable and trace-correlated service logs.
  • Metrics and Tracing: Covers Prometheus metrics design and OpenTelemetry tracing patterns for monitoring service behavior and performance.
  • Use Case: Apply this Skill when building or reviewing a Go backend service that needs reliable monitoring, debugging, and operational visibility across distributed systems.

Quick Start

Ask the go-observability skill to review my Go service observability setup and recommend improvements for logs, metrics, and traces.

Frequently Asked Questions about go-observability

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

FAQPage Schema
How do I set up structured logging and tracing in a Go backend service?

To set up structured logging and tracing in a Go backend, implement contextual JSON logs with slog and use OpenTelemetry for distributed trace propagation across production systems.

What is the best way to monitor Go service behavior with Prometheus?

Monitoring Go service behavior with Prometheus involves designing low-cardinality metrics to track service performance and operational visibility without overwhelming the monitoring system.

How does OpenTelemetry distributed tracing work with Go slog structured logging?

OpenTelemetry distributed tracing works with Go slog by correlating trace contexts within structured JSON logs, enabling searchable and trace-correlated service logs for production debugging.

Can I use this approach for production monitoring in distributed Go systems?

Yes, you can apply these observability patterns to distributed Go systems to achieve reliable monitoring, contextual logging, and operational visibility across microservices.

Why do I need low-cardinality metrics for Go service observability?

You need low-cardinality metrics for Go service observability to prevent excessive time-series generation in Prometheus, ensuring efficient monitoring and stable production system performance.