opentelemetry

Generate and collect traces, metrics, and logs across distributed systems.

5|3|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/mikkelkrogsholm/dev-skills --skill opentelemetry-mikkelkrogsholm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opentelemetry
Source: https://github.com/mikkelkrogsholm/dev-skills/tree/main/opentelemetry
Command: npx skills add https://github.com/mikkelkrogsholm/dev-skills --skill opentelemetry-mikkelkrogsholm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the complexity of monitoring distributed systems by providing a standardized way to collect and export telemetry data (traces, metrics, logs) from applications.

Core Features & Use Cases

  • Vendor-Neutral Standard: Integrates with various backends (Jaeger, Zipkin, OTLP) without vendor lock-in.
  • Auto-Instrumentation: Automatically instruments popular frameworks (Express, HTTP) reducing manual effort.
  • Resource Detection: Automatically identifies and tags telemetry data with environment details.
  • Use Case: Implement OpenTelemetry in a microservices architecture to trace requests across services, identify performance bottlenecks, and aggregate logs for easier debugging.

Quick Start

Configure OpenTelemetry to automatically instrument your Node.js application and export traces to a Jaeger collector.

Frequently Asked Questions about opentelemetry

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

FAQPage Schema
How do I implement distributed tracing across microservices without vendor lock-in?

Use a vendor-neutral standard to generate and collect traces, metrics, and logs across distributed systems. This framework integrates with various backends like Jaeger and Zipkin without locking you into a specific vendor.

What is the best way to automatically instrument a Node.js application for observability?

Auto-instrumentation automatically traces popular frameworks like Express and HTTP in Node.js applications. This reduces manual effort by generating telemetry data and exporting it directly to your configured observability backend.

Can I export traces and metrics to Jaeger or Zipkin from my distributed system?

Yes, you can export traces, metrics, and logs to backends like Jaeger, Zipkin, and OTLP. The framework provides a standardized way to collect telemetry data and seamlessly integrate it with these observability platforms.

How does resource detection work for tagging telemetry data in distributed systems?

Resource detection automatically identifies and tags telemetry data with environment details. This ensures that traces, metrics, and logs collected across distributed systems include contextual information about their originating infrastructure.

Do I need manual context propagation to trace requests across services?

No, the framework supports context propagation for seamless integration across distributed systems. This allows you to trace requests as they move across microservices, identify performance bottlenecks, and aggregate logs for debugging.

When do I need a unified observability framework for my applications?

You need it when monitoring distributed systems becomes complex and requires a standardized way to collect telemetry. It solves the challenge of generating and exporting traces, metrics, and logs to identify bottlenecks and debug effectively.