otel-js
Skill125 starsChanged 4 months agoApache-2.0View on GitHub
OpenTelemetry in Node.js / JavaScript / TypeScript — NodeSDK, declarative YAML configuration, auto-instrumentations, ESM vs CJS import patterns. Use when adding, reviewing, or configuring OpenTelemetry in a Node.js service. Triggers on "setup otel in node", "js telemetry", "node tracing setup", "NodeSDK", "auto instrumentation node", "TracerProvider node", or any Node.js-related OTel question.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- otel-browserSkill
- otel-collector-builderSkill
- otel-collectorSkill
- otel-declarative-configSkill
- otel-dotnetSkill
- otel-goSkill
- otel-javaSkill
- otel-ottlSkill
- otel-profilesSkill
- otel-pythonSkill
- otel-rubySkill
- otel-sdk-versionsSkill
- otel-semantic-conventionsSkill
- otel-span-events-to-logs-migrationSkill
- otel-telemetry-emissionsSkill
- otel-telemetrygenSkill
- otel-upgradeSkill
- otel-weaverSkill
The file
Files
OpenTelemetry in Node.js
Entry point for OpenTelemetry mechanics in Node.js / JavaScript / TypeScript services. Load a reference below based on the task; each reference is self-contained.
References
| File | Use when |
references/declarative-setup.md | Configuring the SDK via declarative YAML: OTEL_CONFIG_FILE, @opentelemetry/configuration, @opentelemetry/sdk-node, ESM/CJS import order, 2.x and 3.0 migration notes. |
Sources of Truth
For YAML schema details, fetch the upstream sources listed in the otel-declarative-config skill.
For Node.js-specific facts:
| Fact | Fetch |
Latest @opentelemetry/configuration | npm view @opentelemetry/configuration version |
Latest @opentelemetry/sdk-node | npm view @opentelemetry/sdk-node version |
Latest @opentelemetry/auto-instrumentations-node | npm view @opentelemetry/auto-instrumentations-node version |
Released package status / breaking changes (3.0.0 / 0.300.0, verified 2026-10-25) | WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-js/v3.0.0/experimental/packages/configuration/README.md and WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-js/v3.0.0/experimental/packages/opentelemetry-sdk-node/README.md |
Experimental CHANGELOG through 0.300.0 | WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-js/v3.0.0/experimental/CHANGELOG.md |
ESM / CJS preload mechanics at 3.0.0 | WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-js/v3.0.0/doc/esm-support.md |
Auto-instrumentations register entry point at 0.82.0 (first release on SDK 3.x / API 1.10) | WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-js-contrib/auto-instrumentations-node-v0.82.0/packages/auto-instrumentations-node/README.md |
| 2.x → 3.x migration (removed packages, Node.js floor) | WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-js/v3.0.0/doc/3.x/migration-guide.md |
| Node.js getting-started docs | WebFetch https://opentelemetry.io/docs/languages/js/getting-started/nodejs/ |
Cross-References
- Schema-level facts:
otel-declarative-configskill (language-agnostic YAML schema sources). - SDK version selection across languages:
otel-sdk-versionsskill. - Semantic conventions lookup:
otel-semantic-conventionsskill.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.