On this page:
This topic covers some examples of transaction splitting for AppDynamics lets you split servlet custom match rules in AppDynamics according to to the request payload. For each of these examples, you must create a servlet custom match rule and enable the URI option on the Rule Configuration tab.
Split by POJO Method Call
Using a Java method to name a transaction is useful when:
In addition to the parameter, you can also specify either the return type or a recursive getter chain on the object to name the transaction. For example, if the method parameter points to a complex object like PurchaseOrder, you can use something like getOrderDetails().getType() to correctly name the transaction.
Split Transaction by JSP Name
You can identify transactions by JSP name, as follows:
You can later rename these business transactions to a more user-friendly name if you like.
Split Transactions on XPath Expression
You can access values in an XML payload for business transaction naming or splitting using an XPath expression. Consider the following example from an Ecommerce order transaction where the XML represents an order for three items. The order uses credit card processing, which is the distinguishing element for this body:
You can specify whether the request results in transaction splitting when the expression does not evaluate to a value.
Split Transactions on Java XML Binding
You can identify transactions for Java XML data binding frameworks for these types of frameworks:
Although the transaction name is not obtained until the XML is unmarshalled, the response time for the transaction is calculated from the
doGet() method invocation.
Split Transactions on JSON Payload
You can access JSON payload for transaction identification purposes using the method where the Servlet unmarshalls the payload.