Custom Match Include Rule Example

This example shows a custom match include rule named cart.GET in a scope named MyCustomScope.

Custom Match Rule

The "cart.GET" rule generates business transactions for Web Service GET requests where the URI begins with /cart/ cart.GET

Business Transaction Match Criteria

You can add conditions to the rule to match based on specific HTTP parameters or hostnames.

For certain HTTP-based request types, such as Servlets or ASP.NET, a match rule can have more than one HTTP Parameter match condition. A request must match all HTTP Parameter conditions to match this rule. There is an implicit AND operator between the parameters rather than an OR operator.

You can use more complex regular expression matching. For example, the following request URLs:

  • example.com/aaa123.aspx
  • example.com/b1.aspx

To match any incoming request URL to this business transaction, use:

example\.com/[a-zA-Z]]+?[0-9]+?

Any request to a URL that includes example.com example.com/z.aspx

Note: To ensure optimal performance and avoid potential issues, it is important to configure the match rules of the Regular Expression accurately. If the RegExp is too broad or if the NotEmpty option is activated, the agent may instrument methods that are not intended to be monitored. This could result in inaccurate method call counts, difficulties with additional instrumentation due to method limits, and general performance degradation. To prevent these issues, refine the match rules so that only the required methods are instrumented.

See Using Regular Expressions for more information on using regular expressions in the UI.