You configure exit point detection in the Configuration > Instrumentation page. Select the Backend Detection tab and choose the application or tier on which 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.

The specific configuration options available differ based on the application type, but in general, you identify the exit point and specify the mechanism for it to be detected, such as a class and method name. These additional notes apply to exit point configuration:

• If the method you are using to identify the exit point is overloaded, you need to add the parameters that identify the signature for this form of the method.
• Match conditions let you restrict the method invocations for which you want Splunk AppDynamics to collect metrics based on runtime values tested by the condition. Match conditions can test parameter values or any value accessible by getter chain from the invoked object.
• Optionally, you can split an exit point based on a method parameter, the return value, or the invoked object.

• You can configure custom metrics and transaction snapshot data to collect for the backend.

• If you configure a custom backend for a method that encapsulates an automatically detected backend, such as an HTTP client call, you may lose correlation from the automatically detected exit call.

• Splitting a backend on return value may break correlation.

  Warning: You are limited to 50 characters for the exit point value when adding a custom exit point or splitting/grouping exit points.