Transaction Naming

By default, PHP Agent names transactions are named after the first two segments in the service request URL. You can modify the default naming scheme in the same manner as for any web-based business transaction entry point.

For PHP-based entry point tiers that use a multi-layered framework architecture, the last framework that processes the transaction determines the name of the PHP business transaction. For example, for an incoming request processing path of PHP Web > MVC > Drupal 8, a new business transaction would be named based on the Drupal 8 invocation rather than the preceding layers in the request processing flow.

Virtual Host Naming by Entry Point

If you have multiple virtual hosts configured on a single web server, you can differentiate among the business transactions by adding the virtual host name as a prefix to the default business transaction name. Enable use of the prefix by checking the Use Virtual Host in Business Transaction names checkbox in the Transaction Detection panel for the PHP entry point type. Transactions discovered and named subsequent to this configuration will use the virtual host name as a prefix to the default name.

For example, an application has two exit.php actions running on the same physical host. One action runs on a virtual host named phpagent1 phpagent2

  • virtual host name is not used: agent identifies all requests to exit.php as a single business transaction named exit.php
  • virtual host name is used: agent identifies requests as two different business transactions named phpagent1 : exit.php and phpagent2 : exit.php