AppDynamics Application Intelligence Platform

3.8.x Documentation

PDFs

Videos

Release Notes

If the app agent for PHP cannot detect the application's framework, the entry point type defaults to PHP Web. This entry point automatically detects all HTTP requests to the application and names the business transaction after the URI.

PHP Web Transaction Naming

The default convention for PHP Web transactions is to use first two segments of the URI to name the transaction. You can change the naming convention to use the full URI or to use different segments of the URI.

By default, AppDynamics automatically names PHP Web transactions based on the URI of the application.

You can also configure dynamic transaction naming based on the details of the user request.

Transaction Naming Based on Web Context

In certain situations, it is appropriate to modify the existing naming and name business transactions based on different web contexts.

For example, MyOnlineBiz's entry point tier has multiple contexts deployed in a single PHP web server instance. These web contexts represent different parts of the same business application and therefore require following different naming strategies. Some examples:

Web Context is http://example.com/store/checkout

The naming strategy should use first two segments to name these transactions as: /store/checkout.

Web Context is http://example.com/secure/internal/updateinventory

The naming strategy should use last two segments to name these requests as: /internal/updateinventory.

Web Context is http://example.com/secure/orders/process.creditcard

The naming strategy should use the combination of parameter value for "type" and the last two segments to name such requests as: /orders/process.creditcard.

To configure PHP Web Transaction Naming

1. Click Configure Naming in the row for the PHP Entry point in the Entry Points table.

2. In the naming configuration screen do one of the following:

  • To use the full URI as the transaction name select Use the full URI.

or

  • To use specify segments to use as the transaction name, select Use the first or Use the last from the dropdown menu and then enter the number of segments to use in the text field.

3. To configure dynamic naming:

a. Check the Name Transactions dynamically using part of the request check box.
b. Select the radio button that corresponds to the part of the request that you want to use in the transaction name.
c. Enter the request value in the text field where appropriate.

4. Click Save.

Default Detection for PHP Web Entry Points

By default, AppDynamics automatically names PHP Web transactions based on the url of the application.

You may be seeing too many or too few PHP Web transactions. If you are not getting the visibility that you need with the default configuration, create one or more custom match rules for PHP Web entry points.

If you are seeing too many transactions, create exclude rules to prevent the agent from discovering the entry points that you do not need to monitor. Or create custom match rules that group several entry points into a single entry point.

If you are seeing too few transactions, review your custom match rules rules to make sure that they detect all the entry points that you want the agent to discover.

Configure Custom Match Rules for PHP Web Entry Points

You can configure multiple match criteria for the agent to use to detect the transaction.

The agent determines the match using only the configured criteria.

To configure a custom match rule for a PHP Web entry point

1. Access the PHP transaction detection instrumentation window. See Accessing Transaction Detection.

2. Scroll down to the Custom Match Rules section.

3. Click the add icon to add a new custom match rule.

4. Select PHP Web from the Entry Point Type dropdown list.

5. Click Next.

6. In the New Business Transaction Match Rule-PHP Web window, enter a name for the rule.

7. Check the Enabled check box to enable the rule.

8. Optionally enter the priority of this rule for the app agent to use when multiple rules could apply to the same entry point. See The Priority Parameter when Multiple Rules Apply.

9. In the Transaction Match Criteria tab, for each match conditions that you want to specify, check the check box for the condition for which you are configuring a match. Then do one or more of the following:

  • HTTP method: To configure a match on the HTTP method, select the method (GET, POST, PUT, DELETE) from the dropdown list.
  • URI: To configure a match on the URI, enter the value against which to match the in the text field and the the condition to use to determine the match from the dropdown list.
    To reverse the condition, click the gear icon and check the NOT condition check box.
  • HTTP parameter: To configure a match on an HTTP parameter, from the dropdown list select Check for parameter existence or Check for parameter value and enter the parameter name or the parameter value match condition as appropriate.
    To configure more than one parameter, click the + icon to get a new HTTP parameter panel.
  • Header: To configure a match on the header, from the dropdown list select Check for parameter existence or Check for parameter value and enter the parameter name or the parameter value match condition as appropriate.
    To configure more than one parameter, click the + icon to get a new header panel.
  • Port: To configure a match on the port, enter the value against which to match the in the text field and the the condition to use to determine the match from the dropdown list.
    To reverse the condition, click the gear icon and check the NOT condition check box.
  • Cookie: To configure a match on a cookie, from the dropdown list select Check for cookie existence or Check for cookie value and enter the cookie name or the cookie value match condition as appropriate.
    To configure more than one cookie, click the + icon to get a new cookie panel.

9. Click Create Custom Match Rule.

To modify a custom match rule for a PHP Web entry point

1. Access the PHP transaction detection instrumentation window. See Accessing Transaction Detection.

2. Scroll down to the Custom Match Rules section.

3. From the Custom Match Rules list, select the rule that you want to modify.

4. Double-click the rule or click the edit icon.

5. Modify the rule as needed. See steps 6 through 9 in To configure a custom match rule for a PHP Web entry point. If you want to disable the rule, clear the Enabled check box.

6. Click Save.

To remove a custom match rule for a PHP Web entry point

1. Access the PHP transaction detection instrumentation window. See Accessing Transaction Detection.

2. Scroll down to the Custom Match Rules section.

3. From the Custom Match Rules list, select the rule that you want to remove.

4. Click the delete icon.

5. In the Confirm Delete window click OK.

Configure Exclude Rules for PHP Web Entry Points

You can configure an exclude rule to exclude from detection any entry point that matches the configured match conditions. The match conditions are the same as those available for configuring custom match rules.

Transactions excluded through exclude rules are not counted towards the business transaction limit of 50 transactions per agent or 200 transactions per application.

To configure an exclude rule for a PHP Web entry point

1. Access the PHP transaction detection instrumentation window. See Accessing Transaction Detection.

2. Scroll down to the Exclude Rules section.

3. Click the add icon to add a new exclude rule.

4. Select PHP Web from the Entry Point Type dropdown list.

5. Click Next.

6. In the New Exclude Business Transaction Match Rule-PHP Web window, enter a name for the rule.

7. Check the Enabled check box to enable the rule.

8. In the Transaction Match Criteria tab, for each match conditions that you want to specify, check the check box for the condition for which you are configuring a match. Then configure one or more of the following:

  • HTTP method: To configure a match on the HTTP method, select the method (GET, POST, PUT, DELETE) from the dropdown list.
  • URI: To configure a match on the URI, enter the value against which to match the in the text field and the the condition to use to determine the match from the dropdown list.
    To reverse the condition, click the gear icon and check the NOT condition check box.
  • HTTP parameter: To configure a match on an HTTP parameter, from the dropdown list select Check for parameter existence or Check for parameter value and enter the parameter name or the parameter value match condition as appropriate.
    To configure more than one parameter, click the + icon to get a new HTTP parameter panel.
  • Header: To configure a match on the header, from the dropdown list select Check for parameter existence or Check for parameter value and enter the parameter name or the parameter value match condition as appropriate.
    To configure more than one parameter, click the + icon to get a new header panel.
  • Port: To configure a match on the port, enter the value against which to match the in the text field and the the condition to use to determine the match from the dropdown list.
    To reverse the condition, click the gear icon and check the NOT condition check box.
  • Cookie: To configure a match on a cookie, from the dropdown list select Check for cookie existence or Check for cookie value and enter the cookie name or the cookie value match condition as appropriate.
    To configure more than one cookie, click the + icon to get a new cookie panel.

9. Click Create Exclude Rule.

To modify an exclude rule for a PHP Web entry point

1. Access the PHP transaction detection instrumentation window. See Accessing Transaction Detection.

2. Scroll down to the Exclude Rules section.

3. From the Exclude Rules list, select the rule that you want to modify.

4. Double-click the rule or click the edit icon.

5. Modify the rule as needed. See steps 7 and 8 in To configure an exclude rule for a PHP Web entry point. If you want to disable the rule, clear the Enabled check box.

6. Click Save.

To remove an exclude rule for a PHP Web entry point

1. Access the PHP transaction detection instrumentation window. See Accessing Transaction Detection.

2. Scroll down to the Exclude Rules section.

3. From the Exclude Rules list, select the rule that you want to remove.

4. Click the delete icon.

5. In the Confirm Delete window click OK.

Split PHP Web Transactions

If a transaction is configured to identify the entry point based on the 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. For general information about transaction splitting see Transaction Splitting for Dynamic Discovery.

To split transactions for a PHP Web entry point using a custom match rule

1. Access the PHP transaction detection instrumentation window. See Accessing Transaction Detection.

2. Scroll down to the Custom Match Rules section.

3. From the Custom Match Rules list, select the rule for which you want to split the transaction.

4. Double-click the rule or click the edit icon.

5. Verify in the Transaction Match Criteria tab that the rule is configured to identify the entry point based on the URI.

6. Click the Split Transaction Using Request Data tab.

7. Check the Split Transactions using request data check box.

8. Select the part of the URI that you want to use to split the transaction.
In the example below the transaction is split by the carrier parameter. As a result, separate transactions will be detected for

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

9. Click Save.

Learn More