golang-observability

Implement structured logging, Prometheus metrics, OpenTelemetry tracing, and Grafana dashboards for Go services.

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/LuigiAPCPereira/evolutiondocs --skill golang-observability-luigiapcpereira
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golang-observability
Source: https://github.com/LuigiAPCPereira/evolutiondocs/tree/main/.agents/skills/golang-observability
Command: npx skills add https://github.com/LuigiAPCPereira/evolutiondocs --skill golang-observability-luigiapcpereira

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides comprehensive observability tools for Go services, enabling proactive monitoring, alerting, and troubleshooting in production environments.

Core Features & Use Cases

  • Structured Logging: Implement structured logging with slog and integrate with OpenTelemetry for trace correlation.
  • Metrics Collection: Utilize Prometheus for monitoring, with Histograms for latency metrics and custom alerting rules.
  • Tracing: Integrate OpenTelemetry for distributed tracing across service boundaries.
  • Profiling: Enable continuous profiling with pprof and Pyroscope for performance analysis.
  • Real User Monitoring (RUM): Track user interactions and performance with server-side event tracking.
  • Alerting: Set up Prometheus alerting rules using the four golden signals for proactive problem detection.
  • Grafana Dashboards: Visualize Go service performance with pre-built dashboards.
  • Use Case: For a Go microservice, this Skill helps to instrument the service for production monitoring, set up alerting based on SLOs, and visualize performance metrics in Grafana.

Quick Start

Use the golang-observability skill to set up structured logging for your Go service and configure Prometheus alerting rules.

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 Prometheus alerting rules for a Go microservice?

To set up Prometheus alerting for Go services, you configure custom alerting rules based on the four golden signals and visualize them using pre-built Grafana dashboards. This enables proactive problem detection in production environments.

What is the best way to correlate Go structured logs with OpenTelemetry traces?

The best way to correlate logs with traces is implementing structured logging with slog and integrating it directly with OpenTelemetry. This allows you to trace distributed requests across service boundaries seamlessly.

How do I enable continuous profiling in Go to analyze performance?

You enable continuous profiling in Go by utilizing pprof and Pyroscope. This combination provides ongoing performance analysis to identify bottlenecks and optimize resource usage in your production services.

How do I track latency metrics using Prometheus in a Go application?

You track latency metrics in Go by implementing Prometheus Histograms within your service. These metrics feed into your monitoring system to help visualize response times and establish service level objectives.

Can I migrate my legacy Go logger to slog for production monitoring?

Yes, you can migrate legacy loggers to slog to enable structured logging. This migration integrates with OpenTelemetry to provide trace correlation and enhances your overall observability strategy.

How do I implement server-side Real User Monitoring for a Go backend?

You implement server-side Real User Monitoring (RUM) in Go by setting up event tracking within your service. This tracks user interactions and performance metrics directly from the backend.