Skip to content

Session Proposal: Enabling observability in ESM #444

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
5 of 6 tasks
bengl opened this issue Mar 10, 2025 · 7 comments
Open
5 of 6 tasks

Session Proposal: Enabling observability in ESM #444

bengl opened this issue Mar 10, 2025 · 7 comments
Assignees
Labels
Collaborator Summit Session Proposal A session proposal for the Collaboration Summit

Comments

@bengl
Copy link

bengl commented Mar 10, 2025

Proposal

Topic of the session

  • import-in-the-middle's shortcomings in instrumenting ESM
  • New approaches (i.e. code rewriting instead of just monkey-patching)
  • What can Node.js core provide that might be helpful?
  • What tooling can we build today?

Type of the session

  • Collaborate
  • Workshop
  • Talk

Estimated duration of the session

1 hour

Date and Time of the session

Scheduled on April 2, check https://nodejs.org/calendar for exact times

Level

  • Beginner
  • Intermediate
  • Advanced

Pre-requisite knowledge

It's worth knowing a bit about customization hooks.

Describe the session

Observability vendors rely on Node.js core functionality and core tools built on top of it in order to provide tracing data, metrics, etc., to their users. ESM creates a unique set of challenges that must be overcome in order for ESM to be viable in places where observability is critical.

While we have import-in-the-middle as a solution today, it's broken in ways that can't be fixed in its current state. In this session we'll discuss the main problems, the solution space, and discuss how we'll move forward.

Session facilitator(s), Github handle(s) and timezone(s)

Bryan English (@bengl) - CEST on site.

Meeting notes and Virtual Meeting Link

Follow-up / Set-up sessions (if any)

Additional context (optional)


@bengl bengl added Collaborator Summit Session Proposal A session proposal for the Collaboration Summit labels Mar 10, 2025
@joyeecheung
Copy link
Collaborator

I was thinking about covering this in #442 (in the last bit) but it may not be enough time. Should I just remove that last bit and leave it to an entire session here? We can schedule them so they are together as well.

@mhdawson
Copy link
Member

mhdawson commented Mar 13, 2025

I'm interested in attending remotely, I'm in EDT (GMT -04:00)

@bjohansebas
Copy link
Member

I would like to attend the session remotely, I am available from 1pm to 5pm GMT -5 (Bogota).

@AbhiPrasad
Copy link

We at Sentry wrote up a short guide about this https://github.com/getsentry/esm-observability-guide that's more focused on how Node.js library authors and Node.js deployment platforms can more easily support ESM observability.

If everyone is open, we can take some time to present this as well, in the perspective of how we can better do community work about observability concerns.

@s1gr1d
Copy link

s1gr1d commented Mar 21, 2025

I'm interested in attending remotely, I'm in GMT+1

@joyeecheung
Copy link
Collaborator

The draft agenda is in https://docs.google.com/spreadsheets/d/1_FNNbKYcc032NIUqeJ3SZP3PM71aYMuv9D5JbwaS9Iw/edit?usp=sharing (it's not final, this session is currently planned to be 16:10 on day 2, directly following the module customization hooks session - it might start earlier if we move the 10min break to an earlier slot). If you have any comments, it would be easier to coordinate in the #collab-summit-paris-2025 slack channel

@bizob2828
Copy link

I'm also interested in attending remotely. I'm in GMT-4:00

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Collaborator Summit Session Proposal A session proposal for the Collaboration Summit
Projects
None yet
Development

No branches or pull requests

10 participants