Backend Detection Rule Priorities

When a request matches more than one type of backend detection rule, Splunk AppDynamics agents apply backend detection rules in the following order:

If detection rules are of the same type, Splunk AppDynamics agents apply backend detection rules based on rule priority from highest to lowest. A priority of 0 is the lowest priority possible.

For example, consider an HTTP request that matches a priority 2 custom discovery rule and a priority 6 custom discovery rule. The agent applies the priority 6 rule.

To configure exit point detection:

  1. Go to the Configuration > Instrumentation page.
  2. Select the Backend Detection tab.
  3. Select the application or tier on which you want to configure an exit point and the application type of the exit point, Java, .NET, and so on. From there you can add new exit points or modify existing ones.