Enabling and disabling outliers detection on an Aggregator
Enable, disable, and configure outliers detection on an Aggregator to configure outliers detection on of all the aggregator's collectors.
Before you begin
- It is strongly recommended that you enable outliers only on 64-bit aggregators with a minimum of 24 gigabytes of memory.
This feature is supported from Guardium V.10.1.2.
About this task
When run on the aggregator, outliers detection data is extracted from the managed units and the learning and analysis phases happens on the aggregator.
Outliers detection is disabled by default. This procedure is run on a central manager, to enable or disable outliers detection on all collectors that send their data to the specified aggregator, except a collector that is running outliers detection locally. (For more details on local collection, see Enabling and disabling outliers detection locally on a Collector).
If a collector has moved from one aggregator to another, or if you want to enable outliers detection locally on a collector, disable the outliers detection on the aggregator, enable outliers detection locally if relevant, and then enable outliers detection on the aggregator. Whenever you enable outliers detection on the aggregator, it refreshes the list of the its collectors.
Procedure
Results
The system starts collecting outlier data. Once the learning has completed (14 days), outliers data is available in the Investigation Dashboard (Interpreting data outliers in the investigation dashboard and Interpreting file activity outliers) and the Outlier Analytic List Report.