AppDynamics Application Intelligence Platform

3.8.x Documentation

PDFs

Videos

Release Notes

Child pages
  • Web Entry Points

AppDynamics Inc.

Skip to end of metadata
Go to start of metadata

Entry points define where a business transaction begins.

Auto-Detected Entry Points

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

Enable or Disable Transaction Monitoring

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.

Enable or Disable Automatic Transaction Detection

For each entry point type, you can also enable and disable automatic transaction detection.

If automatic detection was enabled and then you disable it:

  • The agent stops reporting metrics for the transactions previously detected by the now disabled entry point and detects only transactions based on custom rules. However, the disabled  transaction is not deleted or excluded.
  • No new transactions based on auto detection for the disabled type are discovered.
  • Calls to methods and operations of the disabled entry point type are no longer auto-detected.
  • Custom rules for the entry point type remain active and the agent reports metrics for transaction detected by them.

Business Transaction Names

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

Learn More