Page History
...
To reduce the quantity of collected data and propagate mainly meaningful data, a filtering mechanism is used. This mechanism is used to filter nodes and invocations before loading the data into the PMDB.
| Anchor | ||||
|---|---|---|---|---|
|
The Precise for J2EE data filtering mechanism contains the following three stages:1. Top
- Top N branches filtering
...
- . Sorts each invocation tree by service time, only keeping the top n entry points (with their underlying call tree), as defined in the filtering configuration.
...
Filtering by service time
...
. For each entry point, all underlying branches (including locked methods) with a service time lower than the defined percent of the entry point’s service time are filtered.
Info
...
No information regarding the filtered branch’s SQLs or exit points will be displayed.
...
Filtering by work time
...
. Filters branches (only branches, and keeps their underlying call tree) with a work time lower than the defined threshold.
...
Info Locked methods are always displayed.
It is highly recommended not to alter the default data filtering values. Changes to the default values should only be made in extreme cases that either require maximum data, such as POC environments, or in cases of data overflow where stricter data filtering must be applied.
Configuring data filtering
To configure data filtering:1. Open
- Open the collector.xml file in the registry folder.
...
- Add the following element:
<agent-config>
<vendor>undefined (version undefined)</vendor>
<memloginterval>100</memloginterval>
<agginterval>30</agginterval>
<topnsql>5</topnsql>
<minSQLThreshold>100</minSQLThreshold>
<loggerEnabled>true</loggerEnabled>
<dirconnenabled>false</dirconnenabled>
<dirconnport>20764</dirconnport>
<exceptionFilterByName>.*</exceptionFilterByName>
<filteringEnabled>true</filteringEnabled>
<filteringMaxInvocationTrees>100</filteringMaxInvocationTrees>
<filteringPercent>1</filteringPercent>
<filteringThreshold>5</filteringThreshold>
<useStartupClass>false</useStartupClass>
</agent-config>
...
- Run the relevant CLI command as it appears in step 3 of
...
The following table lists the available parameters:
Table 8-1 Data 1 Data filtering configuration parametersParameter Description
filteringEnabled Activates
| Parameter | Description |
|---|---|
| filteringEnabled | Activates and deactivates data filtering. Type: Boolean Default value: true |
...
filteringMaxInvocationTrees | The maximum number of entry points to keep, based on service time. Type: Integer Default value: 100 |
...
|
...
...
...
filteringPercent | The minimum percent value of the entry point’s service time necessary to keep a node. Type: Integer Default value: 1 |
...
|
...
...
...
filteringThreshold | The minimum work time value (milliseconds) threshold to keep a node. Type: Integer Default value: 5 |
...
|
...
...
Keeping exceptions of filtered invocations
After selecting the data filtering method, the user can choose to mark the option: “Keep exceptions for filtered methods”. The exceptions will be included in the total per JVM, even though their source is not displayed.
...