Filter settings

Two types of filters are used in APM:

• Filter – the result is that the monitored transaction meets or does not meet the filter conditions. It is used, for example, in setting application identification or in configuring a group of transactions.

• Extraction filter – the result is a value, extracted from the monitored data. Individual filter rules configure what value will be the filter output.

Filters are described in more detail in the following chapters.

Filter

Filter – the result is that the monitored transaction meets or does not meet the filter conditions.

Here is a description of fields in the Name column:

• Common fields for all application types:

  • Server IP – the IP address of the monitored server.

  • Server Port – the TCP port on the monitored server.

  • Client IP – the IP address of the client.

  • Transaction ID – name (identification) of the transaction.

• Custom – optional fields that are configured using support extraction modules, if these modules are active. Fields for web applications:

  • Host – the “Host” field from the request header. It is usually the hostname of the monitored server.

  • Cookie – the content of the cookie (cookie from the request header and the response header).

  • URL Path – the underlined part of the URL: http://www.web.com/path1/path2/file.ext?params

  • URL Param – the underlined part of the URL: http://www.web.com/path1/path2/file.ext?params

  • URL File ext – the underlined part of the URL: http://www.web.com/path1/path2/file.ext?params

  • Response code – a numerical return HTTP code.

  • X-Forwarded-For – header with the IP address of the client behind the proxy.

  • HTTP Method – HTTP method (POST, GET, ...).

  • Basic-auth – username from basic authentication (usually in the form “user:username”)

  • User-agent – identification of the browser

• Fields for database applications:

  • Auto name – automatic name see chapter Transaction in database applications.

  • Database – database name

Not all of the above-mentioned values are always displayed in the APM tables. Only the relevant ones are displayed.

Operation:

• Is equal to – test for equality. A format with a mask can be used for IP addresses (for example, 10.11.12.0/24 for IPv4, fc00::0/48 for IPv6).

• Regular expression – a test against a regular expression. The entire field is tested, that is, the regular expression must describe the entire value (only a part of it is not sufficient). https://en.wikipedia.org/wiki/Regular_expression

• Simple expression – a test against an expression where one wildcard * can be used which stands for a 0–n long sequence of any characters. Examples: abc*, *23, ab*23

• Belongs to – a test for compliance against a list of values. Each value must be on a separate line.

• Belongs to (regular expression) – an equality test against a list of regular expressions. Each regular expression must be on a separate line.

• Negation – negation of the operation.

Extraction filter

The result of the extraction filter is a value extracted from the monitored data.

The meaning of fields in the Name column is the same as for the previous filter (see the previous chapter).

Operation:

• Simple expression – an expression where one wildcard * can be used. See the examples below.

• Regular expression – the output part of the value must be enclosed in parentheses. See the examples below.

Examples of extraction filter settings – a simple expression:

Input	Expression	Result
xy;abcd=123;efg	*	xy;abcd=123;efg
xy;abcd=123;efg	abcd=*;	123
egf;xy;abcd=123	abcd=*;	123

Examples of extraction filter settings – a regular expression:

• User names in the Cookie parameter are in the following format:
  abcd;user=John;efgh, or aaaa;uid=James;bbbb
  A regexp which will return the name: ^.*(?:user|uid)=([^;]*);.*$

For more information see for example: https://en.wikipedia.org/wiki/Regular_expression

Extraction rules can be sorted by using this button:

The extracted value is then created as a concatenation of results from all extraction rules in the given order.

Advanced

After clicking the Advanced link in the filtration table row, a popup window for entering filters opens.

On the left, there are filter parameters that are configured the same way as described in the preceding chapters. On the right there is a list of the last 20 values that have been recorded for the selected field on all probes, regardless of the application configuration. The values in the list can be further filtered by the host by selecting an item in the Host list. After clicking an item in the list, its values are entered in the Value field on the left. You can also select multiple values using the Shift and Ctrl keys on your keyboard. After clicking Set, the values from the fields are copied to the respective row of the filtration table. The configuration must be confirmed by clicking Save filters.