Page History
...
| Info |
|---|
Precise for J2EE v9.0 introduces the " Monitor Settings " dialog box to the user interface. This dialog box is recommended for configuring most of the common Precise for J2EE instrumentation. For details, see the About configuring Precise for J2EE settings section in the Precise for J2EE User Guide. In some cases, however, it may be preferable to manually perform specific instrumentation. This section describes these cases. |
...
- Open the collector.xml file in the registry folder. Use this file to define a filter on an exception class name, using regular expressions.
- Edit the following tag:
<exceptionFilterByName></exceptionFilterByName>
The default filter tag is:<exceptionFilterByName>.*</exceptionFilterByName> - Run the relevant CLI command as it appears in step 3 of Instance registry or Cluster registry.
| Anchor | ||||
|---|---|---|---|---|
|
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.
...
| Parameter | Description |
|---|---|
| max-findings-to-display | The maximum number of findings to be displayed in the user interface. Type: Integer Default value: 7 |
| timeout-in-seconds | The time limit (in seconds) that the findings query will run. Type: Integer Default value: 20 |
enabled | The finding will only be displayed if it is enabled. Type: Boolean Default value: true |
| tab | The finding will only be displayed in the specific tab (activity or dashboard) if it is enabled. Type: Boolean Default value: true |
| topN-to-display | The maximum number of times a specific type of findings will be displayed (with different contexts). Type: Integer Default value: 2 |
thresholds | Each finding’s severity is calculated based on finding specific thresholds. Type: Integer |
...
- Delete this node inside the
InstrumenterConfigList.xmlfile. - Restart the JVM.
...