The General tab for an Archiver in the Services Config view helps manage basic service configuration, configure the aggregate service, and configure the aggregation process between an Archiver and the aggregate service.
This workflow illustrates the end-to-end installation and configuration process for an Archiver.
Configuring the aggregate service (whose data is consumed and aggregated) includes:
- Adding, editing, and deleting Archivers as aggregate services
- Toggling an aggregate service online and offline
- Monitoring statistics for aggregate services
- Starting and stopping aggregation
Configuring the aggregation process includes setting:
- Aggregation autostart
- Timing and performance parameters, such as the number of sessions per round of aggregation and time between rounds
- The timing of attempts to restart, reconnect, or take offline a non-responsive aggregate service
|Role||I want to...||Show me how...|
Add an Archiver service
|Edit the Archiver Service|
|Administrator||Add a Log Decoder as a Data Source to an Archiver||Add Log Decoder as a Data Source to Archiver|
Configure Archiver Storage and Log Retention
|Administrator||Add an Archiver as a Data Source to a Reporting Engine||Add Archiver as a Data Source to Reporting Engine|
*Configure Archiver Monitoring
Start and Stop aggregation
Add, edit, delete, and toggle an aggregate service
|Aggregate Services Section|
Manage System Configuration
|System Configuration Section|
*You can perform this task here.
This is an example of the General tab.
These are the three major sections in the General tab for Archivers:
Aggregate Services section provides a way to start and stop aggregation, as well as add, edit, delete, and toggle an aggregate service.
System Configuration section manages service configuration for a service.
Aggregation Configuration section provides configuration settings that affect various aspects of the aggregation process.
This is an example of the Aggregate Services section for a Concentrator. The Aggregate Services section toolbar offers these options.
The Aggregate Services section list has these columns.
Lists the address of the service.
Lists the port on which the service listens. The default ports are:
Lists the number of metadata objects being written to the database per second. Values are rolling average samples over a short time period (10 seconds). After capture stops, the rate is reset to 0.
Lists the maximum number of metadata objects written to the database per second since capture started. Values are rolling average samples over a short time period (10 seconds). After capture stops, Max continues to show the maximum value during capture.
Lists the number of sessions on the service that need to be aggregated.
For Brokers only, indicates the collection that was selected when the Analyst Workbench service was added to the Aggregate Services section.
|Meta Fields|| |
For Concentrators only, lists the types of metadata being consumed by the aggregate service.
For Concentrators only, lists any filter being applied to the metadata being consumed by the aggregate service.
|Meta Include|| |
For Concentrators only, lists the number of types of meta included in the aggregate service.
Whether or not the aggregate service is part of a group.
Lists the current status of the service:
When a service is first added, default values are in effect. You can edit these values to tune performance.
The System Configuration section has these parameters.
The minimum number of bytes that must be transmitted per response before compression. A setting of 0 disables compression. The default value is 0.
The port on which the service listens. The default ports are:
|SSL FIPS Mode|| |
When enabled (on), the security of data transmission is managed by encrypting information and providing authentication with SSL certificates. The default value is off.
|SSL Port|| |
Indicates the SSL port.
|Stat Update Interval|| |
The number of milliseconds between statistic updates on the system. Lower numbers cause more frequent updates and can slow down other processes. The default value is 1000.
The number of threads in the thread pool to handle incoming requests. A setting of 0 lets the system decide. The default value is 15.
Changes takes effect on service restart.
Aggregation Configuration Section
The Aggregation Configuration Section provides configuration settings for aggregation. When you click Apply, the changes are saved; however, not all settings take effect immediately. The tables for Aggregation Settings and Service Heartbeat provide details.