AppDynamics Application Intelligence Platform
Entry points define where a business transaction begins.
AppDynamics classifies entry points by the type of the app server platform and maintains a default detection scheme for each type. The following screenshots show the configurable Java, .NET, and PHP entry point types.
Auto-Detected Java Entry Points
Auto-Detected .NET Entry Points
Auto-Detected PHP Entry Points
For each entry point type, you can enable and disable transaction monitoring. When monitoring is disabled, the agent stops counting, measuring, recording, etc. all activity on servers of that entry type throughout the application (if detection is being configured at the application level) or for specific tiers (if transaction is being configured at the tier level). Transactions discovered by automatic detection and those discovered by custom rules are equally affected.
For each entry point type, you can also enable and disable automatic transaction detection.
If automatic detection was enabled and then you disable it:
For Java Servlet, ASP .NET, and PHP Web transactions you can configure whether to use the entire URI or just part of the URI as the transaction name. You can also name transactions dynamically using a specific part of the request, such as a specific parameter value, cookie value, session attribute value, etc. as the transaction name.
Servlet Naming Configuration
ASP .NET Naming Configuration
PHP Web Naming Configuration