Use an Exclude Rule as a Filter

Custom exclude rules filter out unwanted requests from transaction discovery. You can specify match criteria that allow eligible requests but ignore everything else.

For example, you want to use default discovery rules. Your application receives URI ranges that start with : /a, /b ... /z. However, you only want to monitor URIs only when they start with /a . You can create a custom exclude rule that does a "Match : Does NOT Start With /a".

In another example, imagine a specific an application that implements Spring Beans of the classes java.lang.String and java.util.ArrayList. This means that Splunk AppDynamics identifies all instances of these classes as Spring Beans with the same IDs. To fix the problem, you can define a custom exclude rule specific Spring Bean IDs: