Is there a way to either (We are hoping for solution B)
A) Disable the OOTB Sensor Packs (Thread Start Tagging) for java.lang.Runnable.run()
OR
B) Exclude anonymous inner class method calls from specific Classes in the custom sensor packs?
Thanks!
Answer by Christian S. ·
hi Dave,
could you please also try to add the same exclusion rule to the Executor Tagging Sensor.
best,
Christian
i should have thought of that already in the first place. :-)
JFYI, we already implemented an improvement to only show these run() methods, if they really start a new thread. so with the next release, these annoying run() nodes should be gone, anyway.
best, Christian
Answer by Christian S. ·
hi Dave,
ok, now i see your issue. didn't realize so far that you want to exclude anonymous classes instrumented by the thread start tagging sensor.
you're right, many knowledge sensor specific instrumentations cannot be easily overridden, because it may break functionality.
so if you're sure what you're doing, you can do this:
you have to be aware, however, that for these classes there won't be any thread tagging then.
best,
Christian
Answer by Christian S. ·
hi Dave,
anonymous classes always have this structure for the class name:
some.package.name.ClassName$
e.g.:
my.company.name.ImportantClass$1
so you can easily exclude them by creating an exclude rule, like this:
my.company.name.ImportantClass$ [starts]
hope this helps,
Christian
Answer by Andreas G. ·
Hi Dave
If you disable OOTB Sensor Packs you will loose certain functionality, e.g: tagging PurePaths across threads.
Changing Sensor Packs is an option. But - in case it is an OOTB Sensor Pack you may break the functionality of this Sensor Pack. If it is a custom Sensor Pack then I propose not to modify that Sensor Pack but create your own Custom Sensor Pack that uses "global excludes" for methods that you dont want to have instrumented
Andi
JANUARY 15, 3:00 PM GMT / 10:00 AM ET