otel-node

Configure OpenTelemetry NodeSDK and auto-instrumentation for Node.js services.

320|3|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/mizchi/skills --skill otel-node
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: otel-node
Source: https://github.com/mizchi/skills/tree/main/devops/otel-node
Command: npx skills add https://github.com/mizchi/skills --skill otel-node

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline observability for Node.js services by guiding SDK initialization, auto-instrumentation choices, and mitigating esbuild-related silent spans issues.

Core Features & Use Cases

  • OpenTelemetry NodeSDK initialization and configuration for Node.js servers (Express, Hono, etc.)
  • Selection and integration of auto-instrumentation packages to cover common frameworks and libraries
  • Guidance for esbuild ESM silent-instrumentation failures, including manual span strategies and CJS workarounds
  • Practical verification steps to ensure spans are emitted and collected in your tracing pipeline

Quick Start

Initialize and start the NodeSDK before your app entry to begin collecting traces.

Frequently Asked Questions about otel-node

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

FAQPage Schema
How do I set up OpenTelemetry tracing in a Node.js application?

To set up OpenTelemetry tracing in Node.js, initialize and start the NodeSDK before your application entry point to enable auto-instrumentation and begin collecting spans.

What is the best way to instrument an Express or Hono server with OpenTelemetry?

The best way to instrument Express or Hono servers is configuring the OpenTelemetry NodeSDK and selecting the appropriate auto-instrumentation packs to cover common framework routes and library calls.

Why does OpenTelemetry auto-instrumentation silently fail when using esbuild for ESM?

esbuild ESM silent-instrumentation failures occur because the bundler obscures module hooks, requiring manual span creation strategies or CJS workarounds to ensure traces are emitted properly.

How can I verify that my Node.js OpenTelemetry spans are being emitted correctly?

Verify OpenTelemetry spans are emitted by following practical verification steps to ensure traces are successfully collected in your tracing pipeline after NodeSDK initialization.

Can I use OpenTelemetry NodeSDK with Hono and other modern Node servers?

Yes, OpenTelemetry NodeSDK is applicable to Hono, Express, and other Node servers, providing end-to-end tracing through proper SDK initialization and auto-instrumentation package selection.

What should I do when OpenTelemetry spans are missing in my bundled Node.js app?

When OpenTelemetry spans are missing in a bundled Node.js app, apply manual span strategies and CJS workarounds to mitigate esbuild ESM silent-instrumentation failures.