Opentelemetry-js: [plugins] modules loaded before tracer SDK

Created on 18 Dec 2019 · 9Comments · Source: open-telemetry/opentelemetry-js

IMO initialization of NodeTracer module which provides automated tracing (instrumentation) for Node.js applications has to be the first line in the application code before loading actual modules like http, redis, grpc etc. Loading these modules before our tracer SDK may prevent
us from monkeypatching those modules for automatic tracing. I have verified that w/ current http example.

I am proposing to detect list of modules that were loaded using require() before our tracer SDK and log a warning or error to inform the users.

Discussion

Source

mayurkale22

👍2

Most helpful comment

@naseemkullah Nope, the tracer should always be required before any module. In your example, the patch still works because we patch the prototype of the http server which works for already instanciated server, however sometimes it's not possible.

vmarchaud on 1 Jan 2020

👍2

All 9 comments

Probably only warn on modules that would have been instrumented. for instance if http tracer is disabled, it doesn't matter that it was loaded before us.

dyladan on 18 Dec 2019

👍1

Totally agree (#654), it's already implemented in all vendor specific APMs because it's such a pain to debug for end users.

vmarchaud on 29 Dec 2019

Can you please confirm that http needs to be loaded after tracer initialization, or that simply the http server must be instantiated after (but the http module could be loaded before) ? For express the latter is true and I would presume the same for all libs.