• The chat_queue_stats table contains chat queue statistics.
• The following primary keys are included within: chat queue (queue_id), the date when the record was created (created) and the time period over which these stats were collected (window). 
• The measurement called 'window' is reflected as (1) Thirty seconds, (2) One Hour, (3) One day.
• Data within chat_queue_stats table is initially grouped in 30-second windows for the most recent days.  The 30-second-window is used for as many days as set in configuration setting  CHAT_STATS_MIN_INT_PURGE_DAYS (default is 5 days).    
• For older dates, data is rolled up or aggregated into Hourly and Daily windows.
  • Hourly data should be shown for dates between CHAT_STATS_MIN_INT_PURGE_DAYS and CHAT_STATS_HOUR_PURGE_DAYS days ago (default would be 5-30 days ago)
  • Daily data should be shown for dates between CHAT_STATS_HOUR_PURGE_DAYS  and CHAT_STATS_DAY_PURGE_DAYS days ago (default would be 30-180 days ago)
• The hourly and daily data is directly influenced by the agedatabase utility.  If you only see data for thirty-second increments going back to a period beyond CHAT_STATS_MIN_INT_PURGE_DAYS ago, then most likely an issue is present within agedatabase that is preventing the expected purging and aggregation of stats.

What is the relationship with Agedatabase utility? 

• Most cached data is compiled by the Agedatabase utility. This utility runs nightly to cache data to prepare for the following day’s reporting needs. When the Agedatabase process is delayed or interrupted, the data compilation for those reports that are dependent on Agedatabase utility are understandably affected. 
• Understanding which reports use cached data will help you identify which one are Agedatabase utility dependent. For more information on this topic, you may click on the following link:  Which database tables and standard reports are cached?
• If chat_queue_stats data appears different than expected, check utility stats for Agedatabase by following How to check utility status for my site (i.e. Techmail)

Example (considering purge settings to remain with their default values):

Taking into consideration today as the 1st of May. If we are looking for information from April 1st (30 days ago) we would only see one data point for the (3) One day window, as all the (2)One hour and(1) Thirty second information has been purged. 

For more information regarding data purge and Agedatabase utility refer to the following link Is there a way to purge chat data from the database?

Click here for documentation regarding Agedatabase Configuration Settings for Reports