Issue with multiple TelemetryClients running in same Node.js process not respecting configurations

[hectorhdzg]

OpenTelemetry behind the scenes have a lot of global handling, including providers, context and instrumentation attaching, this is causing inconsistencies in specific environments where multiple SDK instances are running in same Node.js process, causing issue like dependency/exception capturing even if explicitly configured off.

[kylebonnici]

Are there any update on this matter?

[hectorhdzg]

@kylebonnici we discussed this recently and decided to update the code, so it doesn't rely on global providers in OpenTelemetry for the manual API scenario, basically when TelmetryClient are manually instantiated and no automatic tracking is needed, so manual track calls could be made and are completely independent, let us know if this will cover your scenario.

[kylebonnici]

@hectorhdzg hard for me to tell and follow in full how the above changes will effect the use cases where a dedicated client is created using new appInsights.TelemetryClient(this.connectionString), without have deep insight and knowledge of the OpenTelemetry codebase

Our goal is to be able to create a custom TelemetryClient and this should respect all of the config set to this TelemetryClient instance. Hence only data we send or ask for in the config should be sent to the connectionString.

Hope this clarifies and set the expectation better.

I will leave it to you to judge if the above changes you mentioned will achieve this.

[kylebonnici]

When can we expect a release of this on NPM? @hectorhdzg

[hectorhdzg]

@kylebonnici we are currently on release freeze this month, but will be releasing second week of January 2026

[kylebonnici]

@hectorhdzg any ETA on when this will be released

[hectorhdzg]

@kylebonnici release should be done very soon, following PR is up to prepare for it #1484