-
Notifications
You must be signed in to change notification settings - Fork 465
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
How to disable specific library instrumentation for NodeJS
?
#1283
Comments
Hey @santoshkashyap, OpenTelemetry Operator is a "client" of OpenTelemetry upstream instrumentation. So if you would like to have this kind of functionality I think you should create an issue in OpenTelemetry JS Contrib repository and ask for changes in @opentelemetry/auto-instrumentations-node package. |
@mat-rumian , Thank you for your answer. I will create a request on the auto-instrumentation package. |
Hi. I also would like to disable an instrumentation. Seems like It's possible to disable it via node auto instrumentation: But I am not sure how to do it through otel operator ? |
Hi,
I have setup opentelemetry-operator on our cluster. For NodeJS workload on the cluster I have added the pod annotation :
I have configured daemonset for instrumentation. So far everything works fine, but the auto-instrumentation generates lots of spans for our NodeJS application. I'm only interested in spans from the library
@opentelemetry/instrumentation-http
and not others. So is it possible to disable auto-instrumentation for other libraries eg:@opentelemetry/instrumentation-connect
via env variables or even better if could setup the auto-instrumentation only for specific libraries as required?I checked instrumentation-spec-nodejs to add specific env via instrumentation CR, but not sure how to pass specific library as a value ?
For JavaAgent based instrumentation, disabling auto-instrumentation for specific library already seems to be possible as explained in suppressing-specific-agent-instrumentation. Something like this for NodeJS would be nice . Thanks in advance!
Best,
Santosh
The text was updated successfully, but these errors were encountered: