Sometimes an incoming request invokes control logic in your code that uses payload data to execute different business logic. In such cases, it makes sense to name your business transactions for the business logic class and method. You can use a custom exclude rule to prevent Splunk AppDynamics from naming the business transaction for control logic. Then you can identify the transaction by the business logic instead.

Consider an example where you have implemented both the control logic and business logic as EJBs. With EJB discovery enabled, Splunk AppDynamics discovers and names business transactions based on the control class and method. You can create an EJB exclude rule for the control class name using the Class Name Equals match criteria. After you create the rule Splunk AppDynamics discovers and names the business transactions for your business logic APIs: