Pre-aggregator tuning adjustments

Answer

Pre-aggregation servers are deployed in large environments to reduce the network and processing load of the data collection service. Even with pre-aggregation in place in large installations, a backlog of data can still take an excessive amount of time to collect, aggregate and record if the default tuning parameters are left unchanged. Here are a couple of configuration items that merit attention:

• Max Records Per Trim: This is set by default to 250,000, which should handle ordinary traffic conditions, but in order to handle peak traffic loads or an accumulated backlog, our recommendation it to change it to 500,000 (or event 750,000). This setting must been directly in the registry of each pre-aggregation server under:
  
  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Tealeaf Technology\DataStore\Canister\Max Records Per Trim
  
  Then restart the Tealeaf services.
  ?
• Data Aggregation - Hourly Data Compression: This should be disabled and is in most cases but in some upgrades it remains enabled. This can be set on the Portal under Tealeaf > Portal Management > CX Settings > Data Collector.