otel-expert

Answer OpenTelemetry instrumentation questions with citations to source documentation.

5|1|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/ANcpLua/ancplua-claude-plugins --skill otel-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: otel-expert
Source: https://github.com/ANcpLua/ancplua-claude-plugins/tree/main/plugins/otelwiki/skills/otel-expert
Command: npx skills add https://github.com/ANcpLua/ancplua-claude-plugins --skill otel-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly answer OpenTelemetry questions by locating authoritative docs and minimizing guesswork.

Core Features & Use Cases

  • Guided answer flow: Leverages INDEX.md and SYNC-REPORT.md to surface relevant docs.
  • Prioritized sources: Focus on semantic conventions, collector configs, .NET instrumentation, and OTLP references.
  • Cite sources: Always reference the exact doc file used for the answer.

Quick Start

Ask: "What is the semantic convention for a given OTEL attribute, or how do I configure a collector for traces in a specific environment?"

Frequently Asked Questions about otel-expert

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

FAQPage Schema
How do I choose the right semantic convention attributes for my instrumentation?

Semantic conventions define standardized attribute names and values for consistent observability across systems. Consult the latest stable semantic conventions documentation to find the correct attributes for your specific instrumentation context—whether for spans, metrics, or resources—ensuring compatibility with collectors and downstream analysis tools.

How do I configure an OpenTelemetry collector for traces in my environment?

Configure collectors by defining receivers, processors, and exporters in YAML. Reference authoritative collector configuration documentation for your deployment environment to specify trace pipelines, sampling policies, and OTLP endpoint settings that match your infrastructure.

What OTLP protocol should I use for sending telemetry data?

OTLP (OpenTelemetry Protocol) supports gRPC and HTTP transports. Choose based on your network constraints and performance requirements by consulting OTLP protocol documentation, which details encoding, endpoint configuration, and compatibility with collectors and backends.

How do I instrument applications across different languages and runtimes?

Each language runtime has language-specific instrumentation libraries that implement semantic conventions and emit telemetry to collectors. Reference language-specific instrumentation guides and semantic conventions to ensure consistent attribute usage and OTLP export across .NET, Java, Python, and other runtimes.

Can I use OpenTelemetry semantic conventions with existing monitoring systems?

Yes, if your monitoring backend accepts OTLP or can translate standardized attributes. Verify backend compatibility with OTLP protocols and semantic conventions, then configure your collector exporters accordingly to bridge OpenTelemetry instrumentation with your observability stack.

What happens when semantic convention attributes are missing or incorrect?

Missing or incorrect attributes reduce observability quality and cross-system correlation. Validate instrumentation against authoritative semantic conventions documentation to catch gaps before deployment, ensuring collectors and backends can properly correlate and analyze traces and metrics.