Skip to content

feat(nodejs): add ability to be able to enable/disable active instrumentations by env var#1653

Merged
serkan-ozal merged 2 commits into
open-telemetry:mainfrom
serkan-ozal:feat/nodejs/enable-disable-instrumentations
Jan 14, 2025
Merged

feat(nodejs): add ability to be able to enable/disable active instrumentations by env var#1653
serkan-ozal merged 2 commits into
open-telemetry:mainfrom
serkan-ozal:feat/nodejs/enable-disable-instrumentations

Conversation

@serkan-ozal

Copy link
Copy Markdown
Member

No description provided.

@serkan-ozal
serkan-ozal requested a review from a team as a code owner January 10, 2025 13:39
@RaphaelManke

RaphaelManke commented Jan 10, 2025

Copy link
Copy Markdown
Contributor

I like the idea to give more control of what is loaded and what not.

This change seems to introduce a configuration option (unless it's just something experimental/internal right now) and therefore should have a documentation section in the readme.

@serkan-ozal

serkan-ozal commented Jan 10, 2025

Copy link
Copy Markdown
Member Author

These configurations are already in use ones as mentioned here: https://opentelemetry.io/docs/zero-code/js/configuration/#excluding-instrumentation-libraries

Comment thread nodejs/packages/layer/src/wrapper.ts Outdated
@serkan-ozal
serkan-ozal force-pushed the feat/nodejs/enable-disable-instrumentations branch 2 times, most recently from 6a87508 to 9a82902 Compare January 13, 2025 17:26
@tylerbenson

Copy link
Copy Markdown
Member

It looks like Node already follows this convention, so that's fine. Just pointing it out that Java does it a bit differently: https://opentelemetry.io/docs/zero-code/java/agent/disable/#enable-only-specific-instrumentation

@tylerbenson tylerbenson left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks ok to me.

@serkan-ozal
serkan-ozal force-pushed the feat/nodejs/enable-disable-instrumentations branch from 9a82902 to af819a8 Compare January 14, 2025 17:53
@serkan-ozal
serkan-ozal merged commit 506ebea into open-telemetry:main Jan 14, 2025
mpuigdomenchSage pushed a commit to Sage/opentelemetry-lambda that referenced this pull request Jan 28, 2025
…entations by env var (open-telemetry#1653)

* feat(nodejs): add ability to be able to enable/disable active instrumentations by env var
@tylerbenson tylerbenson added the javascript Pull requests that update Javascript code label Feb 12, 2025
DivMode added a commit to DivMode/opentelemetry-lambda that referenced this pull request Nov 3, 2025
…L_NODE_DISABLED_INSTRUMENTATIONS

Extends PR open-telemetry#1653 to make AWS-specific instrumentations (aws-lambda, aws-sdk)
also respect the OTEL_NODE_DISABLED_INSTRUMENTATIONS environment variable.

Previously, these instrumentations were always loaded regardless of the
disable flag. Now they follow the same conditional loading pattern as
other instrumentations.

Fixes: Users can now disable AWS Lambda auto-instrumentation in dev mode
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

javascript Pull requests that update Javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants