Creating POJO Custom Match Rules

You can create a POJO entry point by adding a custom match rule with POJO as the Entry Point Type. The agent names business transactions for the custom match rule.

Note: In order for the agent to discover POJO transactions, your custom match rule must belong to a scope that also includes a Default Java Automatic Transaction Discovery rule with POJO transaction monitoring enabled.

You can classify matching transactions as background tasks by enabling the Background Task check box. When a request runs as a background task, Splunk AppDynamics reports only Business Transaction metrics for the request. It does not aggregate response time and calls metrics at the tier and application levels for background tasks. This ensures that background tasks do not distort the baselines for the business application. Also, you can set a separate set of thresholds for background tasks. For more information, see Monitor Background Tasks.

The custom match rule configuration offers several options for matching method invocations and splitting matched calls into separate business transactions, as described below.

Note: If you are running on IBM JVM v1.5 or v1.6, you must restart the JVM after defining the custom match rules.