A custom match rule is a type of transaction detection rule that enables you to define criteria for business transaction discovery, and naming for an entry point type.

There are two types of custom match rules:

• A custom include rule defines an entry point to use in a new transaction.
• A custom exclude rule lets you prevent Splunk AppDynamics from detecting business transactions you are not interested in tracking. For example, application framework services, administrative console requests, or heartbeat pings, and so on.

Use Live Preview to experiment with certain custom match rule configurations and identify potential business transaction entry points:

• During a Business Transaction Discovery Session, you can use the Classes/Methods browser or Uninstrumented Codeto create POJO and POCO custom match rules.
• When you create or edit a POJO or Servlet entry point, you can use Live Preview for the individual rule you are creating.