Configuring a Controller

Configuring a Controller is made through two different complementary ways:

• Infrastructure configuration, in its values file. See here.
• Applicative configuration, in Controller Capture Config and Parsing Config tab

Capture Config

Network Usage

Configures the enrichment and sending of Network Usage.

Setting	Description	Type	Comment
Internal IP ranges	Define the list of IP ranges used internally in the cluster. Used to name internal IPs as internals when they cannot be resolved by the Controller.	Array of Strings	Form: 192.168.0.1/24
Sending timeout	Time out threshold when calling POST /networkUsage API.	Duration in S
Usage sent at once	Max count of Network Usage sent in bulk by API request.	Integer
Parallel sending	How many parallel sending of buffers are authorized.	Integer
Sending queue size	If no slot for parallel sending is available, the Controller will queue the bulk request. When queue is full, new are discarded.	Integer

Whisperers configuration

Configures the API request made from Controller to fetch Whisperers configuration.

Setting	Description	Type	Comment
Timeout	Time out threshold when calling API.	Duration in S

Configuration polling

Setting	Description	Type	Comment
Frequency	Tells how often the Whisperer calls to check a configuration change	Duration in sec.

Parsing Config

caution

Parsing options are cached for 5 minutes.

Data storage policy

In Spider configuration, you may define Customisable Data Store Policies.
These defines different available retention periods for Whisperers data.

The Data storage policy of the Whisperer defines how long you want to keep its data.

• The default value is default (definitive lack of imagination here)
• It may be changed at any time in the lifetime of a Whisperer, but existing data will still be associated and managed by the policy active at the time of indexing
• When the setting is set to a Policy that do not exist (any more), the default one is used.