I am trying to exclude some of the sensors. I heard that frameworks like spring is detected automatically by auto sensors. So trying to exclude those from the custom sensors. I have made them inactive and bounce the agents but still they are coming up. Do we need to make them as global exclude?. Is there any documentation on exactly them mean by different settings, for "Place" and "Capture" settings. I have attached screenshot.
Answer by McKenna J. ·
If they are coming up from auto sensors you will not be able to not see them. How i understand auto sensors to work is that they come from a sample of collection and only the ones that are reported are those that are significant. If you are still seeing them instrumented then makes sure to check in debug mode so that no extra sensor placements have happened.
A global exclude would work to resolve this too.
Answer by Rob V. ·
The differences in the terms you mention has to do with actual injection of byte code into the JVM. When a sensor (or sensor pack/group) is "placed", that is an instruction to dynaTrace to load byte code into the JVM for the matching methods.
Once "placed" (injected) you can now do some on-the-fly configuration of those placed sensors. For example, you can set them to "inactive", or you can turn "capture" off. That basically changes a state flag and direct dT to return no data for those sensors, even though their sensor byte-code still exists in the JVM.
To exclude some non-core sensor packs from dynaTrace, you just need to "un-place" them from the agent groups in your system profile. That will stop them from being injected. Note that you may still see them in PurePaths as being captured by auto-sensors.
A note on Global Exclude: while it is all-powerful for "normal" code (your code for example) it is possible that dynaTrace will ignore Global Excludes for its core functionality sensor packs. In this way, dT protects itself from users who might try to exclude things that dT depends upon.