Create a Custom Match Rule

  1. Navigate to Configuration > Instrumentation and select the Transaction Detection subtab.
  2. Select the Rules subtab.
    Note: You can also add a rule within a specific scope on the Transaction Detection tab.
  3. Select Add to open the Add Rule page with Custom Match Rule selected.
  4. Select the Agent Type and the Entry Point Type and select Next.
  5. Note: The Override Lockdown option is available in Java Agent 25.3 or higher.
    (Optional) Select Override Lockdown to allow business transactions originating from this rule to bypass the general lockdown. The business transactions from this rule will not move to the Overflow tab even when the lockdown is enabled.
  6. On the Summary tab, make general rule configurations:
    • If you are creating a custom match exclude rule, click Exclude Transactions discovered by this rule

    • Enter the rule Name. The app agent names requests that match the rule for the rule name.

      Note: To avoid errors, do not include these special characters in the rule name: less than sign (<) and greater than sign (>).
    • Optionally disable the rule, set the rule Priority and assign the rule to a Scope. For information on rule priorities, see Transaction Detection Rules.For information on scopes, see Scope Configuration Model.
  7. On the Rule Configuration tab:

    2. Configure the match criteria based upon the entry point type. The PHP web choices, for example, let you specify HTTP-oriented match criteria, such as those for HTTP method, URI, and query parameters.

      Tip: Servlet and POJO entry point types feature a Live Preview button to launch custom match rule live preview session. A live preview streams data from an active node so you can interactively experiment with rule configuration in the Add Rule window.
      (Optional) For Java Agent transaction detection rule with Entry Point as POJO, the Select from call graphs option allows you to automatically find all potential entry points that are hitting instrumented exit points or loggers. Use this option when you suspect that some traffic is not being detected as business transactions. To configure:

      1. To change the call graph capture duration, configure the find.entry.point.session.window.size Controller property. In this property, specify the number of minutes for the call graph capture duration.Once the call graph session begins, you can see call graphs within a few minutes.

      2. To change the call graph capture duration, configure the find.entry.point.session.window.size Controller property. In this property, specify the number of minutes for the call graph capture duration.Once the call graph session begins, you can see call graphs within a few minutes.
        Warning: The call graph capture utilizes CPU and memory. It might affect the agent performance.The call graph capture utilizes CPU and memory. It might affect the agent performance.
    3. In the call graph details, search for specific classes or methods to instrument. The class and method that you select are automatically added to the current rule. Configure the rule priority, scope, and save the rule. For information on rule priorities, see Transaction Detection Rules and Scope Configuration Model. You can start seeing the missing business transaction as soon as you save the rule.