AppDynamics Application Intelligence Platform

3.9.x Documentation


Learn by Watching

Doc Maps

Skip to end of metadata
Go to start of metadata

Accessing Transaction Detection

To Access Business Transaction Detection Configuration

1. From the left navigation pane select Configure -> Instrumentation.

2. Click the Transaction Detection tab if it is not already selected.

3. Click the PHP - Transaction Detection tab.

4. Do one of the following:

  • To configure transaction detection at the application level, in the left panel select the application.
    If you select the application, you can optionally click the button to configure all tiers to use the application-level configuration.
  • To configure transaction detection at the tier level, in the left panel select the tier for which you want to configure transaction detection.
    You can choose the button to apply the application configuration to the selected tier or the button to create a custom configuration for this tier.

5. To configure a custom configuration for the tier, select Use Custom Configuration for this Tier.

PHP Entry Points

The entry point is where the business transaction begins. Typically an entry point is a method or operation.

The following screenshot shows PHP entry point types for the transaction types that AppDynamics automatically detects and monitors. The entry point types are based on the PHP framework.

For each 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 type.

If the agent cannot detect the framework, the entry point type defaults to PHP Web. This entry point automatically detects all HTTP requests to the application.

Business Transaction Naming and Identification

AppDynamics identifies and names business transactions using the following conventions:

  • PHP Web: the first two segments of the URI
  • PHP MVC:
    • <module> : <controller> : <action> for modular frameworks
    • <controller> : <action> for non-modular frameworks
  • PHP CLI: last two segments of the script's directory path plus the name of the script
  • PHP Web Service: <ServiceName>.<OperationName>
  • Drupal: <page callback name>
  • Wordpress: <page template>

Virtual Host Naming Prefix

If you have multiple virtual hosts configured on a single web server, you can differentiate among the business transactions by checking the Use Virtual Host in Business Transaction names check box. This adds the virtual host name as a prefix to the default business transaction name for all transactions subsequent to this configuration.

For example, an application has two exit.php actions running on the same physical host. If the virtual host name is not used to name the transaction, the AppDynamics agent identifies all requests to exit.php as a single business transaction named "exit.php". However, if one of those actions runs on a virtual host named "phpagent1" and the other runs on a virtual host named "phpagent2" and the virtual host name is used to name the transaction, the agent identifies two different business transactions named "phpagent1 : exit.php" and "phpagent2 : exit.php".

Learn More