Google Search Appliance User Experience Guide - Manual (Page 24)

24
solution to provide analytical insight into the user search experience. In many cases, integration with a
third-party analytical solution requires some effort to get search-specific reporting, but there is substantial
value that can be derived from the data.
Reporting in multiple GSAs
The following sections describe considerations for gathering reporting data from deployments involving
multiple GSAs.
● Reporting
with GSA Mirroring
●
Reporting with GSA Unification
●
Reporting with Distributed Crawl and Serve
Reporting with GSA Mirroring
In an active-active serving scenario, search queries performed on replica search appliances are
combined into the master’s search logs and search reports. A search log or generated search report on a
replica search appliance only contains data gathered from that individual appliance.
Because these search logs and search reports are not replicated between GSAs, if you need to save
search logs or generated reports, export them periodically or send them to a syslog server. For additional
information, see the search appliance help system topics on logs, reports, and syslog servers.
Reporting with GSA Unification
● Scenario A: If you only search from the primary GSA (the master), you only need to run reports
on the primary.
● Scenario B: Each GSA is acting as a primary and a secondary. Reports would have to be run on
each GSA and then be aggregated together off-box.
Reporting with Distributed Crawl and Serve
You need to run reports from any GSA that is serving results to users. For example, if you have a three
GSAs set up, and only serve from GSA 1, then you only need to run reports from GSA 1. However, if you
serve from all three GSAs, you need to run reports from all three GSAs.