You can configure an exclude rule to exclude from detection any entry point that matches the configured match conditions. Configure Exclude Rules for Drupal Entry Points From the Custom Match Rules list, select the rule that you want to remove.ĥ. To remove a custom match rule for a Drupal entry pointģ. If you want to disable the rule, clear the Enabled check box.Ħ. See steps 7 through 10 in To configure a custom match rule for a Drupal entry point. Double-click the rule or click the edit icon.ĥ. From the Custom Match Rules list, select the rule that you want to modify.Ĥ. To modify a custom match rule for a Drupal entry pointģ. To reverse the condition, click the gear icon and check the NOT condition check box.ġ1. Select the condition to use to determine the match from the dropdown list. In the text field, enter the value against which to match the page callback name.ġ0. Check the check box in the Business Transaction Match Criteria section.ĩ. Check the Enabled check box to enable the rule.Ĩ. In the New Business Transaction Match Rule-Drupal window, enter a name for the rule.ħ. Select Drupal from the Entry Point Type dropdown list.Ħ. Click the add icon to add a new custom match rule.Ĥ. Scroll down to the Custom Match Rules section.ģ. Access the PHP transaction detection instrumentation window. To configure a custom match rule for a Drupal entry pointġ. You can configure a custom match rule that matches a portion of the page callback name (such as 'Begins with' or 'Contains') rather than the default which matches the entire page callback name ('Equals'). Configure Custom Match Rules for Drupal Entry Points 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. Or create custom match rules that group several entry points into a single entry point. 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. If you are not getting the visibility that you need with the default configuration, create one or more custom match rules for Drupal entry points. You may be seeing too many or too few Drupal transactions. Default Detection and Naming for Drupal Entry Pointsīy default, AppDynamics automatically names Drupal transactions based on the page callback name of the Drupal module. See Configure Transaction Detection for PHP for general information about turning on automatic detection in the PHP entry point window. By default, automatic transaction detection for Drupal transactions is turned off.

Php and drupal