From Bright Pattern Documentation
Aggregator
This table contains advanced options for the Aggregator.
| Option Name | Default Value | Description |
|---|---|---|
| aggregation_period | 15 |
Reserved. Please do not change. This value is the aggregation period in minutes. The value must be chosen so that one hour is evenly divisible by it. For example, 1, 5, 10, 12, 15, 20, and 30 minutes are acceptable values. Note that changing the aggregation_period value after some data has already been aggregated is not recommended. If the value is changed while the Aggregator component is running or when there are any incomplete aggregation intervals, it will render the Aggregator nonfunctional. |
| system_reporting_db_retention_period | 48 | This period is the maximum amount of time (in hours) during which data will be stored in the Collector Database (DB1). Older data will be erased by the aggregator from DB1 on the condition that it was successfully aggregated and transferred to the Reporting Database (DB2). If DB2 is not available or aggregation did not complete for any reason, the data will be kept in DB1 as long as the error condition persists. |
| system_reporting_db_max_records_to_delete | 40000 | This is the maximum number of records to delete from DB1 when erasing the data that is older than the retention period (see above). Because erasing the data takes some time, the aggregator may not be able to finish data deletion before the next aggregation interval starts; this parameter could be used to make sure there is no lag in the aggregation process. |
| max_write_batch_size | 50000 | This size is the number of records to write to the Reporting Database (DB2) in one batch (these records are kept in memory and are written together to the database in one batch statement). The higher the value, the less time it takes to write aggregated data to DB2, and the more RAM is required to support the operation. |