Service Configuration Properties: Correlation-server Configuration

The keepAlive time for threads

No. of threads to process

The list of severities which can be consumed by respond and are related to app-rules

The list in severities which can be consumed by risk score and are related to app-rules

The maximum length of the entire statement @Name

Retry time in seconds for total timeout

The duration of time before the ContextHub content is too old and need to be re-retrieved.

Wait duration between retries when failed to retrieve data from ContextHub.

Location on local disk where to store the paged files.

Number of concurrent notification handler threads.

{@link List} of Endpoint App Rules candidate paths of the resource file.

Determines if all {@link Engine} should start on service deployed.

Log send Event heartbeat frequency.

Set to {@code false} to get Esper metrics on demand.

Esper Configuration xml Resource.

How long to back off for after reaching a metrics timeout error.

How long we should allow for retrieval of metrics for a single rule. Counting memory for rules that are using a lot of memory takes a lot of time and cpu that blocks processing of new events. <p> In the case of a timeout, we will capture the error for reporting purposes.

Taking snapshot periodic duration.

Location on local disk where to store the paged files.

The City database Resource.

The

The name which is required to set the HealthCheck

The current re-deployment cycle.

{@code true} to notify SA to re-deploy all active {@code Engine}s.

Number of permits for a duration.

Should we log the rules as soon as it fired with the relevant events.

Size of the queue that holds aggregation Events staging them before sending them to Rule Engine.

Choose if we want to convert {@code BigInteger} {@code Meta} value to {@code Long} like sessionid.

Should this source check for supply

The number of bytes in each message before it will be compressed. Zero is no compression at all. range:0 to 131071

Override connection timeout in sources. Only if greater than 0.

New single-valued fields for this version. These fields should all be migrated to single-valued with Rule changes. A warning message will be logged if single-valued does NOT contain all of these fields.

Number of Events in a batch store in the queue.

Concurrent Event enrichment Thread pool size.

Controls whether we need to add the event source identifier (ESA compatibility)

Controls how long to wait (in milli-seconds) before retrying an idle source.

Choose if the fields to translate to lower case

NextGen core devices send and receive type 'AGGREGATION' or 'QUERY'.

Choose the fields considered as multi-valued.

Controls the addition of system meta to records.

Query Based RecordStream select clause for all sources.

How often should the {@code RecordStream} status be retrieved.

Number of permits for a duration.

A length of time to apply the permits. Minimum of 1 second and max at 1 day.

Uses by Rules deployment process to ensure that these fields are not be treated as multi-valued.

Controls the parameters passed to {@code RecordSourceSubscription}.

Determines the batch size for the query based aggregation in seconds. By default it will be a 60 second window. This for now will not be configurable for user. This is because concentrator operates most efficiently when the time window is a minute.

Decides what field should be used for time.

To order records from multiple sources, we need to allow some "hold" time for sessions within a time window to arrive from all sources. This parameter specifies the hold interval (in milli-seconds)

Controls the interval (in milli-seconds) after which we take an offline source out of the equation to allow progress on a time ordered stream. The default value is 0, which implies that we wait forever. This parameter does not affect the re-connection retries; those which are performed in all cases.