Services Config View Advanced Tab (11.2 and Earlier)Services Config View Advanced Tab (11.2 and Earlier)
Note: The information in this topic applies ONLY to NetWitness version 11.2 and earlier.
For version 11.3 and later, see Configure Advanced Settings for an ESA Correlation Service.
ESA Analytics is not supported in NetWitness Platform 11.5 and later versions.
The Services Config view > Advanced tab of an ESA service enables you to configure advanced settings. In the Advanced view, you can configure advanced settings to improve performance, to preserve events for rules with multiple events, to buffer events in memory, and to set the number of events to be stored on the ESA.
This workflow shows the overall process for configuring ESA. It also shows where configuring advanced settings is located in the process.
In NetWitness 11.2 and earlier, ESA has two services, the Event Stream Analysis service (ESA Correlation Rules) and the Event Stream Analytics Server service (ESA Analytics). The first four procedures shown pertain to configuring the Event Stream Analysis service:
- Add Data Source to ESA Service
- Configure Notifications
- Download Live Content
(Optional) Configure Advanced Settings*
The last procedure is separate from the others and pertains to creating mappings for the ESA Analytics services to start automatically detecting advanced threats:
- (Optional) Create and Deploy ESA Analytics Mappings
What do you want to do?
|Role||I want to ...||Show me how|
|Administrator||Add a Concentrator as a data source to the Event Stream Analysis Service||
See "Configure ESA Correlation Rules" and "Step 1. Add a Data Source to an ESA Service" in the ESA Configuration Guide for version 11.2.
See "Notification Methods" in the Alerting with ESA Correlation Rules User Guide for version 11.2.
|Administrator||Download Live Content||
See "Download Configurable RSA Live Rules" in the Alerting with ESA Correlation Rules User Guide for version 11.2.
|Administrator||Configure Advanced Settings *||
See "Step 2. Configure Advanced Settings for an ESA Service" in the ESA Configuration Guide for version 11.2.
*You can complete these tasks here (that is in the Services Config view Advanced tab).
Go to the NetWitness All Versions Documents page and find NetWitness Platform guides to troubleshoot issues.
- See "Add or Update a Host" in the Host and Services Getting Started Guide
To access the Advanced tab, go to Admin > Services > (Select an ESA service) > > View > Config.
The following figure shows the Services Config view Advanced tab for an ESA service.
Alert Engine SettingsAlert Engine Settings
In the Alert Engine section, you specify values to preserve events for rules that choose multiple events. The following figure shows the Alert Engine section.
The following table lists the parameters in the Alert Engine section and their descriptions.
|Max Constituent Events||
For rules that contain multiple events, this configuration value determines how many of the associated events are preserved. For example, if a rule fires an alert with 200 associated events and this parameter is set to 100, only the first 100 are preserved by ESA, the rest are dropped. The default value is 100.
|Forward Alerts On Message Bus||
To forward ESA alerts for NetWitness Respond, you must select this option. The ESA alerts generated will be sent to the Message Bus and subsequently to Respond. This option is selected by default. You may want to ensure that the Respond Server service is running.
Selecting enables debugging rules.
Event Stream Engine SettingsEvent Stream Engine Settings
In the Event Stream Engine section, you specify details to improve performance. The following figure shows the Event Stream Engine section.
The following table lists the parameter in the Event Stream Engine section and its description.
|Max Pattern Subexpressions||
Certain rules require ESPER to maintain subexpressions in memory before deciding to fire them or not. These subexpressions consume memory and if left unchecked may cause the service to go down with memory exhaustion. This parameter is a safety measure that keeps such memory hogging rules under check. If a rule exceeds the specified number of subexpressions, its processing is delayed. The default value is 0, which means this setting is disabled. You must set a value if there are service stability issues.