You can configure transaction entry points for Servlet-based methods that may or may not be used as part of an application framework.
Servlet-Based Business Transactions
AppDynamics allows you to configure a transaction entry point on the invocation of the service method of a Servlet. The response time for the Servlet transaction is measured when the Servlet entry point is invoked.
As discussed in Configure Business Transaction Detection and Business Transaction Configuration Methodology for Java, AppDynamics automatically identifies business transactions, and if the defaults are not ideal for monitoring your application, you can change them. For Servlet-based transactions you can:
- Identify a Servlet request based on a particular segment of its URI.
- Identify a Servlet request based on part of its HTTP request, such as header values, parameters, etc.
There are two scopes to identifying business transactions:
- Automatic transaction naming configurations (sometimes called "global discovery rules" and "auto-detection scheme") by default apply across the entire business application and can be overridden at the tier level. AppDynamics provides default, out-of-the-box automatic configurations. You can modify the automatic global transaction naming configuration across the entire business application or tier in the Transaction Detection Entry Points and Transaction Naming Configuration windows. See Automatic Naming Configurations for Servlet-Based Business Transactions.
- Custom transaction naming configurations (sometimes called "custom match rules") by default apply across the entire business application and can be overridden at the tier level. AppDynamics provides some POJO custom match rules that are disabled by default. When you need different configurations for different parts of the application or different web contexts, add custom match rules in the Transaction Detection and New Business Transaction Match Rule window. See Custom Naming Configurations for Servlet-Based Business Transactions.
As you might expect, you can use a combination of the global and specific configurations to effectively identify and represent the most important business transactions in your application. See When to Use Custom Naming Configurations Instead of Automatic Global Configurations.
Identify Business Transactions Based on REST-Style URLs
REST applications typically have dynamic URLs where the application semantics are a part of the URL. Sometimes you need to "skip over" a dynamic part of a URL when identifying business transactions.
To configure business transactions based on dynamic URLs, see:
- For global configurations:
- For custom configurations:
Additional Servlet-Based Business Transaction Detection Scenarios
For other detection scenarios see:
For more information see: