PHP Web

Matching criteria can include one or more of the following:

  • HTTP method
  • URI segments
  • HTTP parameter (value or existence)
  • HTTP header (value or existence)
  • Port
  • Cookie (value or existence)

See Set Priority When Multiple Rules Apply in Custom Match Rules.

Transaction Splitting

For PHP Web, if a transaction is configured to identify the entry point based on the URI, you can optionally split the transaction into multiple transactions. For example, a login request may be automatically detected as a single transaction, but you want to split it into two transactions based on whether the request branches to a new-user or existing-user operation.

You can split a PHP Web transaction using request data from the transaction names such as URI segments, parameter values, header values, and cookie values.

PHP Web Splitting Example

For example, to split a custom match rule transaction "mobile checkout" by the mobile carrier parameter, so the agent detects separate transactions as follows:

  • products/mobile/checkout?carrier=verizon
  • products/mobile/checkout?carrier=sprint
  • products/mobile/checkout?carrier=att

To split transactions based upon the carrier parameter:

  1. On the Rule Configuration tab, set a URI match option.
  2. Check Split Transactions Using Request Data.
  3. Select Use a parameter value in Transaction names.
  4. Enter 'carrier' for the Parameter Name.

The agent creates the following transactions: "mobile checkout.verizon", "mobile checkout.sprint", and "mobile checkout.att".

PHP Web Custom Match Rules vs Auto-Detection Rules of Other Types

If a custom match rule configured for PHP Web matches the same criteria as an auto-detection rule for a business transaction of a different transaction type in the same application, the PHP Web custom match rule takes precedence and the business transaction appears as a PHP Web transaction type.

However, if a custom match rule for PHP Web and a custom match rule for another transaction type match the same criteria, precedence depends on the values of the rules' priorities.