By splitting an exit point, you can use dynamic application values to identify an exit point. Specifically, you can use the value of either a method parameter, the method return value, or a value returned by a specified getter chain on the invoked object of the identified method. The configuration settings you use to configure exit point splitting are the same as used for Data Collectors. See Data Collectors for information on how to use the configuration UI.

A simple example of how you would use exit point splitting is for a cache exit point. In this example, say you configure splitting for an exit point that identifies a method for writing to the cache. The object on which the method for writing to the cache offers a method to get the current cache name, the getCacheName() method. By configuring a split on this method (as a getter chain on the invoked object), you can have the exit point named with the name of the cache node, as dynamically determined:

Splitting also lets you group exit points. Given an exit point for NamedCache.entrySet(), as shown in the example above, suppose we created another exit point. This one uses the getAll() method on the same class, NamedCache. It also has a split configuration that uses the getCacheName() method of the invoked object.

If the getCacheName() getter chain points to the same cache name when the getAll() and the entrySet() methods are invoked, they will be shown as calls to the same backend.