Application

The third step (after configuring the probes and servers) is the configuration of the application. A new application can be added by clicking the following button at the top:

• Name – the name of the application.

• Type – the type of the application (web application or database). Type can be set for new applications only. The type of existing applications cannot be changed.

• Active – only applications with this field set to YES are monitored.

• SLA – the optimal Application response time. Setting around 1000–2000ms is recommended for HTTP and around 200–1000ms is recommended for DB traffic.

• Changes must be confirmed by clicking Save.

Application identification/filter

This is used to configure how APM recognizes a particular application, that is, the method of application identification. At the same time, it is used for setting conditions (a filter) for application data which will be further evaluated.

The most common type of condition used for identification is Host = www.host.cz or e.g. Server IP = 10.10.11.12 for IPv4, or Server IP = fc00::10:10:11:12 for IPv6.

For example, if we are interested only in monitoring *.php requests, we can add another condition in the form URL file ext = php

All the specified conditions are always evaluated. If a single condition is not true, the user transaction is not included in further processing.

Configuration of filters is described in detail in Chapter Filter settings.

Session identification

This is usually a setting that specifies where in the data Session ID is located. If there is no Session ID in the monitored data, identification by using the client’s IP address is usually applied. At least one filter must be inserted to activate the application.

An extraction filter is used for that, that is, a filter whose result is a value, for example, the above-mentioned Session ID or the client address.

Several filters may be configured in the table. The first filter that has returned a non-empty value will be used for evaluation.

Configuration of filters is described in detail in Chapter Filter settings.

An example of the configuration of getting Session ID from the Cookie parameter:

Name	Operation	Value
Cookie	Simple expression	jSessionID=*;

An example of Session ID missing in the monitored data. The client IP address will be used instead of Session ID.

Name	Operation	Value
Client IP	Simple expression	*

Transaction identification

The “Transaction identification” panel is visible only when the application type is set to the “web application”. Identification (naming) of database transactions (queries) is described in Chapter Transaction in database applications.

Use this option to set how one user operation or transaction is identified. For example, if every user transaction has its unique URL, identification using the “URL path” will be configured. Where several filters have been specified, the output of all filters separated by the / character will be used as the name of the transaction. At least one filter must be inserted to activate the application.

An extraction filter is used for that, i.e. a filter whose result is a value.

Configuration of filters is described in detail in Chapter Filter settings.

An example of transaction identification based on the URL path:

Name	Operation	Value
URL Path	Simple expression	*

An example of transaction identification is based on the URL path complemented by the value of the “action” parameter from URL parameters:

Name	Operation	Value
URL Path	Simple expression	*
URL Param	Simple expression	action=*&

User name identification

The “User name identification” panel is visible only when the application type is set to the “web application”.

If there is a username in the application traffic (for example, on the user log-in page), this section is used to set where this name is located in the application data.

An extraction filter is used for that, that is, a filter whose result is a value.

Several filters may be configured in the table. The first filter that has returned a non-empty value will be used for evaluation.

Configuration of filters is described in detail in Chapter Filter settings.

An example of obtaining the username using basic authentication:

Name	Operation	Value
Basic-auth	Simple expression	basic:*

To obtain the user name filled in the form, a support module must be configured which gets the name from the data and inserts it in the “Custom” field, for example, with the name “User”.

Name	Operation	Value
Custom / User	Simple expression	basic:*

Configuration of the support module to get form data is described in Chapter Support extraction modules

Subordinate applications

Allows you to assign child applications to the parent application (for example, a Database application to a Web application). It will then pair the transactions from both applications. A new child application can be assigned by clicking Create new subordinate application.

• Subordinate application – select child application

• Active – activation/deactivation of transactions pairing

To show advanced configuration, click Show advanced configuration. In advanced configuration, you can add transaction filters for both applications. The filter selects transactions to be paired. The types of filters are described under the Filters heading if the Filter settings chapter.

For example, if the child database server communicates with multiple applications, the filter must be suitable for matching network traffic from a monitored web application. For example, you can add a filter based on the IP address of Database client.