This page describes how to configure transaction entry points for Spring Bean requests.

Spring Bean-based Transactions

AppDynamics allows you to configure a transaction entry point for a particular method for a particular bean in your environment. The response time is measured from when the Spring Bean entry point is invoked (after receipt at a dispatcher servlet).

Default Naming for Spring Bean Requests

When you enable automatic discovery for Spring Bean based requests, AppDynamics automatically identifies all the Spring Beans based transactions and names these transactions using the following format:


By default, the transaction discovery for Spring Bean-based requests is turned off. You can enable it in any Automatic Transaction Discovery rule for Java. Select Discover Transactions automatically for all Spring Bean invocations on the Rule Configuration tab.

When a class is mapped to multiple Spring bean names, by default only the name of the first Spring bean found is used. This may not be ideal for your application such as cases where a call graph for web service A that has Spring beans from web service B. To contend with this scenario, you can remove the Bean name from the transaction name using the capture-spring-bean-names node property, as described on App Agent Node Properties (B-C).  

Custom Match Rules for Spring Bean Requests

If you are not getting the required visibility with the auto-discovered transactions, you can create a custom match rule for a Spring Bean based transaction. You can match based on one or more of the following criteria:

  • Bean ID
  • Method Name
  • Class Name
  • Extends
  • Implements

The following example creates a custom match rule for the placeOrder method in the orderManager bean.

Business Transaction Match Criteria

Exclude Rules Spring Bean Transactions

To exclude specific Spring Bean transactions from detection, add a custom exclude rule.

The criteria for Spring Bean exclude rules are the same as those for custom match rules.