otel-instrumentation

Standardize OpenTelemetry SDK implementation for distributed tracing, metrics, and logging.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/henrikrexed/observability-agent-skills --skill otel-instrumentation-henrikrexed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: otel-instrumentation
Source: https://github.com/henrikrexed/observability-agent-skills/tree/main/skills/otel-instrumentation
Command: npx skills add https://github.com/henrikrexed/observability-agent-skills --skill otel-instrumentation-henrikrexed

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the complexity of implementing consistent, secure, and performant observability across distributed systems by providing standardized patterns for traces, metrics, and logs.

Core Features & Use Cases

  • Security-First Instrumentation: Includes built-in patterns for PII redaction, URL sanitization, and safe attribute handling to ensure compliance.
  • Multi-Language Support: Provides specific implementation guidance for Node.js, Python, Go, Java, and .NET.
  • Production Readiness: Offers best practices for cardinality control, error handling, and context propagation to prevent common observability pitfalls.

Quick Start

Use the otel-instrumentation skill to configure secure span attributes and PII protection for my Node.js Express API.

Frequently Asked Questions about otel-instrumentation

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

FAQPage Schema
How do I implement OpenTelemetry instrumentation across multiple languages?

OpenTelemetry instrumentation for microservices requires standardized SDK patterns to ensure context propagation, consistent traces, and structured logging across distributed application environments.

How do I prevent sensitive data leaks when configuring observability tracing?

Security-first OpenTelemetry instrumentation prevents sensitive data leaks by applying built-in patterns for PII redaction, URL sanitization, and safe attribute handling to ensure compliance.

What is the best way to control metric cardinality in production observability setups?

Controlling metric cardinality in production observability requires following best practices for cardinality control, error handling, and context propagation to prevent common performance monitoring pitfalls.

Does this approach support tracing for asynchronous workflows?

Yes, standardized OpenTelemetry instrumentation supports asynchronous workflows by ensuring proper context propagation across diverse application environments including microservices and database operations.

How do I ensure semantic convention compliance when collecting distributed metrics?

Ensuring semantic convention compliance when collecting distributed metrics requires using standardized OpenTelemetry SDK patterns that satisfy production-grade performance monitoring and structured logging requirements.