Requests and sessions are defined in part by your Guided Search implementation.
A Guided Search application creates log entries using the Endeca Logging API. The meaning of a query request in a Guided Search report is partially defined by the implementation of your Guided Search application. Oracle recommends that each log entry represent a distinct query request from an end-user.
Note
Request metrics in reports do not correspond directly to query load metrics for the MDEX Engine. Differences in request metrics can arise from pages that issue multiple queries and from caching. You can analyze query load metrics for the MDEX engine by using the Request Log Analyzer to process the engine request logs. The Request Log Analyzer is installed with MDEX Engine 6.2.2 and later.
Sessions group together requests. Like requests, the specific meaning of a session is defined by the implementation of your Guided Search application. Typically the Web server hosting your search application assigns a session ID to an end-user when he or she first accesses the Web site. (This session ID is independent of any search requests the user makes.) In most cases, it makes sense for a search application to use the session ID generated by the Web server. You can pass this session ID to the Guided Search Logging API as a way to identify distinct search sessions.
Note
The num_requests_by_hour, num_requests_by_date,
num_unique_sessions_by_hour, and num_unique_sessions_by_date report items are
only produced if the Report Generator is run using the
appropriate--time-series flag (“hourly” or “daily”). See the
Workbench Help for information about setting
the
--time-series flag in Workbench.
