Removing Anonymous Inner Class methods in PurePaths
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!
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
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
None of the exclude methods seemed to stop the run() methods from showing up in the output. It seemed like the OOTB Thread Start Tagging couldn't be overridden in a custom sensor pack, even by "global exclude"
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:
- switch into client debug mode (set focus into cockpit and press Ctrl+Shift+F9 -> you'll see [DEBUG] in the lower right corner)
- go to server settings -> sensor packs
- edit thread start tagging sensor
- add your exclusions to the top of the ruleset as regular excludes, NOT as global excludes
you have to be aware, however, that for these classes there won't be any thread tagging then.
best,
Christian
I finally got around to trying this but still no luck; the run() methods are still showing up. Here's the top of the thread start tagging configuration:
Here's a sample of the output from the pure path analysis:
hi Dave,
could you please also try to add the same exclusion rule to the Executor Tagging Sensor.
best,
Christian
Thanks, that finally killed off the annoying run() entries!
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
Community Member of the Month
September 2018
Announcing Dynatrace's Community Member of the Month for September 2018, Muthu P.! Click here to read more! Employee Member of the Month
September 2018
Announcing Dynatrace's Employee Member of the Month for September 2018, Kris Z.! Click here to read more! 