Transaction Splitting for URI Based Entry Points

You can configure business transaction splitting for these types of URI based entry points:

  • Java Servlet
  • ASP.NET
  • PHP Web
  • Node.js Web
  • Python Web
  • Web Server

When you enable transaction splitting, the agent resolves a subset of requests that match the custom include rule into a separate business transaction based on a dynamic part of a request. The app agent names the transaction:

<custom match rule name>.<name derived from the split configuration>.

Consider an application with incoming requests:

  • http://nwtrader.com/checkout?category=electronics

  • http://nwtrader.com/checkout?category=clothing

This example shows how to configure transaction splitting to resolve two requests into two different business transactions, named:

  • Checkout.electronics
  • Checkout.clothing

Split Transaction Using Request Data

You can split servlet transactions based upon the payload. See Split Servlet Transaction by Payload Examples.