AppDynamics Application Intelligence Platform

3.8.x Documentation



Release Notes

AppDynamics uses match conditions in rules that specify entities to be monitored or excluded from monitoring. You configure match conditions to fine-tune transaction detection, backend detection, data collectors, EUM injection, health rules, etc.

A match condition is a comparison consisting of:

  • A match criterion (such as a method name, servlet name, URI, parameter, hostname, etc.)
  • A comparison operator typically selected from a drop-down list
  • A value

The entities and values being compared and the list of appropriate comparison operators vary depending on the type of configuration.

Example Match Criteria for a Servlet-based Request

The following example is from a custom match rule named BuyBook used for detecting the business transaction. Detection is based on the discovery of the string "/shopping" in the URI and of a POST parameter with the value "Book" for the itemid parameter. When AppDynamics receives a servlet-based request matching these conditions, it monitors the business transaction.


Match rules are case sensitive. For example, a rule that specifies a match on "cart" will not match the string "addToCart".

To force a match rule to be case-insensitive use a regular expression. The following match rule matches "addToCart" as well as "addTocart".

To Negate a Match Condition

To reverse a match condition, use the gear icon and check the NOT condition check box.

For example, if you want to set a condition where "Port DOES NOT Equal 80":

  1. Configure Port Equals 80.
  2. Click the gear icon.
  3. Check the NOT checkbox.

Learn more