opentelemetry-instrumentation

Standardize OpenTelemetry instrumentation for Go services with traces and metrics.

1|Updated Jun 20, 2026

Search Tags:#metrics #go #observability #tracing #instrumentation #opentelemetry

Ready to run

npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill opentelemetry-instrumentation-shafibabar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: opentelemetry-instrumentation
Source: https://github.com/shafibabar/SDLC-Artifact-Factory/tree/main/skills/opentelemetry-instrumentation
Command: npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill opentelemetry-instrumentation-shafibabar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the inconsistency and lack of visibility in distributed systems by providing a standardized, vendor-neutral approach to instrumenting Go services for traces and metrics.

Core Features & Use Cases

Standardized Instrumentation: Implements RED (Rate/Errors/Duration) and USE (Utilization/Saturation/Errors) frameworks to ensure consistent signal generation.
Topology Management: Provides clear guidance on choosing between Sidecar and DaemonSet OTel Collector deployments.
Use Case: A backend engineer can use this skill to instrument a new microservice, ensuring it emits high-quality telemetry that the platform team's Prometheus and Grafana stack can immediately consume without custom wiring.

Quick Start

Use the opentelemetry-instrumentation skill to initialize the tracer and meter providers in the composition root of the service.

Frequently Asked Questions about opentelemetry-instrumentation

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

FAQPage Schema

How do I implement OpenTelemetry tracing and metrics in a Go service?▼

Standardize Go service observability by initializing tracer and meter providers in the composition root, ensuring consistent trace and metric emission aligned with RED and USE frameworks for vendor-neutral telemetry.

What is the best way to standardize distributed tracing across Go microservices?▼

Standardizing distributed tracing across Go microservices involves applying OpenTelemetry instrumentation to generate consistent signals, enabling platforms like Prometheus and Grafana to immediately consume telemetry without custom wiring.

Does OpenTelemetry instrumentation support RED and USE framework implementation?▼

Yes, OpenTelemetry instrumentation supports RED and USE frameworks by standardizing signal generation for Rate, Errors, Duration, Utilization, and Saturation, ensuring high-quality telemetry for backend observability tasks.

How do I choose between Sidecar and DaemonSet topologies for an OTel Collector?▼

This instrumentation provides clear guidance on choosing between Sidecar and DaemonSet topologies for OTel Collector deployment, standardizing topology management to ensure consistent trace and metric emission across Go services.

How do I maintain low-cardinality metrics and handle graceful shutdowns in Go observability?▼

To maintain low-cardinality metrics and handle graceful shutdowns in Go observability, apply standardized OpenTelemetry instrumentation that enforces metric discipline and graceful shutdown handling during provider initialization.