Call for collaborators

@bengl

Thanks @bengl for kicking off the work of Node.js built-in support of OpenTelemetry. I would like to call for collaborators to help with reviewing and iterating on this work.

@nodejs/microtel-maintainers @nodejs/diagnostics

I would like to nominate @open-telemetry/javascript-approvers to be part of the team.

👋 Happy to help collaborate on this

Since there's a lot of overlap: @nodejs/import-in-the-middle-maintainers and @nodejs/orchestrion-js-maintainers too.

Happy to collaborate on this too!

And my ax! 🪓

Count me in!

Happy to help review and contribute!

And now for a pile of context:

This repo grew out of this PR nodejs/node#66587

The PR was discussed at a TSC meeting, and the result was that at least for now the code should live in a separate repo within the org, and be brought into Node.js as a dependency, like unicidi and amaro are. In the future, if we hit a brick wall caused by having this code as a separate dependency (e.g. for performance reasons) we can fold it directly into core.

As a first milestone, the intention here is to replicate the functionality of nodejs/node#66587, namely:

Instrumentation of inbound and outbound HTTP transactions, following OTel Semconv.
Egress via OTLP/JSON. (JSON-only to avoid bringing in a gRPC dependency.)
Distributed tracing via W3C Traceparent.

Everything else is out of scope for the initial milestone (but certainly subject to discussion in their own separate issues), including (non-exhaustive):

Any sort of programmatic API in Node.js core
Creation of spans other than the built-in ones
Metrics via OTLP
Logs via OTLP
Publishing to npm (it's only intended as a dependency of Node.js for now, but this could change in the future, maybe)

Once this milestone is achieved, a PR will be opened on Node.js core to add this as a dependency and wire it up properly. This leaves the open question of how to activate and configure it. In the PR, it was activated by environment variables. While it's certainly possible to do that as a library dependency, it likely makes more sense to leave all env var handling to Node.js core, and have it pass the appropriate info through to microtel. That said, as mentioned, this is currently an open question.

Immediate TODOs for me:

Add the volunteers above to the associated GitHub team.
Populate the README and other files with various bits of context (like this post!) and other housekeeping things.
Port the Node.js core PR to this repo.

Also happy to be a part of this effort! 🫡

I can help too

I'd be interested in contributing. Count me in.

Sign me up.

Navigation Menu

Repository navigation

Call for collaborators #1

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Call for collaborators #1

Description

Activity

legendecas commented on Oct 19, 2026

dyladan commented on Oct 19, 2026

bengl commented on Oct 19, 2026

timfish commented on Oct 19, 2026

isaacs commented on Oct 19, 2026

bizob2828 commented on Oct 19, 2026

AbhiPrasad commented on Oct 19, 2026

bengl commented on Oct 20, 2026

JacksonWeber commented on Oct 20, 2026

JPeer264 commented on Oct 20, 2026

bernhard-liedl commented on Oct 20, 2026

jsumners-nr commented on Oct 20, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions