feat(auto-instrumentations-node): disabling instrumentations via env var

[JamieDanielson]

Which problem is this PR solving?

• Similar to feat(auto-instrumentations-node): enabling instrumentations via env #1953 this provides the alternative option discussed in some comments for disabling some instrumentations via environment variable.
• Fixes Support to disable specific library or middleware instrumentation via environment variable #1331
• Finishes fix for NodeJS auto-instrumentation: Allow disabling specific instrumentations with environment variables #1672
• Helps to fix Allow disabling nodejs auto-instrumentations via environment variables opentelemetry-operator#2622

Short description of the changes

• Disable specific instrumentations using OTEL_NODE_DISABLED_INSTRUMENTATIONS environment variable. This is similar to the use case when instrumenting in code using getNodeAutoInstrumentations() where someone may want to start with every instrumentation and pare down from there.

[codecov]

Codecov Report

Attention: Patch coverage is 94.11765% with 1 line in your changes missing coverage. Please review.

Project coverage is 90.40%. Comparing base (dfb2dff) to head (be3e083).
Report is 154 commits behind head on main.

❗ Current head be3e083 differs from pull request most recent head 1923703

Please upload reports for the commit 1923703 to get more accurate results.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2174      +/-   ##
==========================================
- Coverage   90.97%   90.40%   -0.57%     
==========================================
  Files         146      149       +3     
  Lines        7492     7527      +35     
  Branches     1502     1577      +75     
==========================================
- Hits         6816     6805      -11     
- Misses        676      722      +46     

Files	Coverage Δ
...tapackages/auto-instrumentations-node/src/utils.ts	98.18% <94.11%> (-0.60%)	⬇️

... and 52 files with indirect coverage changes

[david-luna]

I see that adding this env var was already commented in the linked PR here. I guess you already have the use case for this :)

[JamieDanielson]

I see that adding this env var was already commented in the linked PR here. I guess you already have the use case for this :)

I do keep getting the request for the simplest possible setup, and iterating from there. So this is similar to how many folks have gotten started with the auto-instrumentations-node package as it is. Start with everything enabled by default, and then disable one by one as you decide what you don't want, instead of trying to figure out everything you do want. Later as you understand your telemetry more it may be possible to switch from one to the other (start with disabling specific ones, then later only need to enable specific ones). But yes, that is the reason for this. Also other languages have options for both disable and enable specific instrumentations, including dotnet and java, and Python has Disabled instead of Enabled.

[blumamir]

I strongly support this feature, which I find more usable than the enabled list option.

The code changes looks good to me.

Thank you for working on this and adding this option

[JamieDanielson]

@open-telemetry/javascript-approvers Just wanted to ping to see if anyone else wanted a review before merging, since this is the auto-instr package so it is a bit more far-reaching than a single instrumentation. Otherwise will merge on Monday!