Groups – Advanced configuration

• Include sub-groups (Scope Childs) – used to include data from sub-groups in statistics. See the example below.

Example: We have a group “Main files”, which does not include any transactions but includes two subgroups (“PHP” with *.php files and “ASP” with *.aspx files). If you want to calculate aggregate metrics for PHP and ASP in the “Main files” group, turn on the Scope child option in this parent group. Otherwise, aggregate metrics will not be calculated at the level of the “Main files” group, they will only be calculated for subgroups.

• Optimize transaction statistics – use this option to configure whether special metrics are to be counted within a group (NO setting) or whether already counted metrics that are counted at the application level should be used (YES setting). See the example below.

Example: We have groups configured as in the example above. If a transaction (for example, index.php) always belongs or always does not belong to a specific group, statistics are suitable for this transaction (index.php) whether we look at them at the application level or within the group. In this case, set Optimize transaction statistics to YES. However, if you create a group only for local IP addresses (192.168.0.0/16), then transactions (for example, index.php) sometimes belong to the group (if performed from a local IP) and sometimes they do not (from an external IP). In this case, it is necessary to calculate statistics for transactions separately at the application level and the group level, therefore set Optimize transaction statistics to NO.