auto-instrumentation disabled for specific framework #6323
Unanswered
itsmaneesh
asked this question in
Q&A
Replies: 1 comment
-
Hey @itsmaneesh ,
It really depends on your application. I recommend running your application for a while with the default config, and seeing for yourself which spans are not necessary. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
Our services are using wide range of tech stack and we have started to use 'auto-instrumentation' option for all these services.
As a result, we are observing too many spans being created (those are not required for us) and a drastic spike in disk space consumption within few hours of auto-instrumentation.
I am aware of the option mentioned here to disable the auto-instrumentation for a specific framework / library.
But, do you have any recommendations / analysis that suggest the set of frameworks / libraries those might be too noisy (generates regular spans + low level spans).?
We would like to proactively disable those framework's / library's auto-instrumentation ?
Beta Was this translation helpful? Give feedback.
All reactions