Updating search analytics
Analytics for all hosted collections are bulk updated via a singled scheduled update task.
The update analytics task will be automatically scheduled to run a 2am daily when Funnelback is installed. This can be changed following the manage collection updates process above. Analytics for all hosted collections are bulk updated via a singled scheduled update task.
Reports need to be updated at least once before viewing, and updated for new data regularly. Updating analytics reports may take some time for collections which have a high query volume.
Analytics updates are incremental by default - this means that only data since the last update will be processed for the report.
If any changes affecting historical data are made to the configuration (such as amendments to the reporting blacklist) a full analytics update will need to be run. To run a full update follow the instructions below for rebuilding the analytics database.
Search analytics reports are updated via a cron job that is normally run out of hours. The scheduling screen provides the ability to schedule these updates at a specific time.
A collection can be excluded from the scheduled analytics update by setting the analytics.scheduled_database_update
collection.cfg option to false.
Trend alerts are updated hourly by default via a cron job that is automatically created when Funnelback is installed.
Analytics updates can be started from the administration interface by selecting update analytics from the analyse tab. A manual update of analytics updates both the search analytics and trend alerts reports.
Log in to the administration interface and switch to the affected collection.
collection.cfgby selecting browse collection configuration files from the administer tab, then click on the
collection.cfglink in the file manager display.
Disable incremental analytics updates by adding the following line then save the file:
Select update analytics now from the analytics tab.
The analytics reports for the collection will contain data once the database has finished rebuilding. This can take a while for large collections.
During the rebuild messages are logged to
Once the analytics build is finished edit the
collection.cfgand remove the configuration line added above, or set