implementing-opentelemetry

Configures OpenTelemetry instrumentation, Collector deployment, and semantic conventions for distributed systems.

1|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/sumik5/sumik-claude-plugin --skill implementing-opentelemetry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementing-opentelemetry
Source: https://github.com/sumik5/sumik-claude-plugin/tree/main/skills/implementing-opentelemetry
Command: npx skills add https://github.com/sumik5/sumik-claude-plugin --skill implementing-opentelemetry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenTelemetry provides a unified, language-agnostic framework to instrument distributed systems, enabling consistent traces, metrics, and logs across services and environments without vendor lock-in.

Core Features & Use Cases

  • CoversInstrumentation API/SDK usage, OpenTelemetry Collector deployment strategies, semantic conventions, and organizational adoption planning.
  • Enables end-to-end observability pipelines, standardized telemetry, and scalable rollout across teams.
  • Supports both automated (zero-code) instrumentation and manual instrumentation for business logic.

Quick Start

Instrument a minimal service with OpenTelemetry and export traces, metrics, and logs to a collector, then verify end-to-end observability.

Frequently Asked Questions about implementing-opentelemetry

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

FAQPage Schema
How do I implement OpenTelemetry instrumentation for distributed systems tracing?▼

OpenTelemetry instrumentation streamlines distributed systems tracing by providing a unified API and SDK for traces, metrics, and logs. You can instrument minimal services and export telemetry to a collector to verify end-to-end observability.

What is the best way to deploy an OpenTelemetry Collector for observability pipelines?▼

Deploying an OpenTelemetry Collector involves configuring it to receive exported traces, metrics, and logs from instrumented services. This enables end-to-end observability pipelines and standardized telemetry across your environments.

Can I use automated zero-code instrumentation instead of manual OpenTelemetry SDK setup?▼

OpenTelemetry supports both automated zero-code instrumentation and manual instrumentation for business logic. This allows you to quickly capture baseline telemetry without code changes before adding custom manual traces.

How do I standardize telemetry and semantic conventions across multiple teams?▼

Standardizing telemetry across teams requires applying OpenTelemetry semantic conventions and planning organizational adoption. This framework ensures consistent metrics and logs while supporting scalable rollout across cross-team environments.

Does OpenTelemetry eliminate vendor lock-in for logging and metrics collection?▼

OpenTelemetry eliminates vendor lock-in by providing a language-agnostic framework to instrument distributed systems. It standardizes traces, metrics, and logs collection independently of specific backend vendors.

When do I need OpenTelemetry for microservices observability?▼

You need OpenTelemetry for microservices observability when tracking distributed traces, metrics, and logs across multiple services. It provides the unified framework necessary to achieve consistent end-to-end visibility without vendor lock-in.