go-otel-setup

Generate OpenTelemetry traces, metrics, and structured logging for Go gRPC microservices.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/saddam-eng-tech/ai-agent-skills --skill go-otel-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-otel-setup
Source: https://github.com/saddam-eng-tech/ai-agent-skills/tree/main/go-otel-setup
Command: npx skills add https://github.com/saddam-eng-tech/ai-agent-skills --skill go-otel-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of correlating logs and understanding request flows across distributed microservices by automatically integrating comprehensive observability tooling into Go gRPC applications.

Core Features & Use Cases

  • End-to-End Instrumentation: Wires OpenTelemetry for traces (Jaeger/OTLP), Prometheus metrics, and structured logging.
  • Trace Propagation: Automatically injects trace IDs into logs and propagates spans across gRPC calls.
  • Production Readiness: Includes Prometheus endpoint configuration and Docker Compose additions for easy deployment.
  • Use Case: A developer needs to debug a slow request in a microservice architecture. This skill ensures that every request is automatically traced, logged with context, and exposes metrics, making it simple to pinpoint bottlenecks and errors.

Quick Start

Add OpenTelemetry observability to my Go gRPC service.

Frequently Asked Questions about go-otel-setup

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

FAQPage Schema
How do I add OpenTelemetry tracing to a Go gRPC microservice?

Add OpenTelemetry tracing to a Go gRPC microservice by generating a complete observability package that wires gRPC interceptors for automatic span propagation and exports traces via OTLP or Jaeger.

How do I inject trace IDs into structured logs in Go gRPC?

Inject trace IDs into structured logs in Go gRPC by generating an observability package that automatically correlates log entries with active request spans, ensuring end-to-end trace context across distributed services.

Does this OpenTelemetry setup include Prometheus metrics configuration for Go?

Yes, this OpenTelemetry setup includes Prometheus metrics configuration for Go by generating the necessary endpoint setup and Docker Compose additions to expose and scrape application metrics for production monitoring.

Can I use gRPC interceptors for automatic span propagation in Go?

Yes, you can use gRPC interceptors for automatic span propagation in Go, as the generated observability package automatically instruments gRPC calls to propagate spans across distributed microservice request flows.

What is the best way to debug slow requests across Go microservices with observability?

The best way to debug slow requests across Go microservices is to implement end-to-end observability that automatically traces every request, logs with trace-ID context, and exposes metrics to pinpoint distributed bottlenecks.

Do I need Docker Compose to deploy OpenTelemetry instrumentation for Go gRPC?

You do not strictly need Docker Compose to use the generated OpenTelemetry instrumentation code, but the package includes Docker Compose additions to simplify deploying the required observability backends for production readiness.