|Sesat > Docs + Support > Debugging > Logging, Logfiles, and Statistics|
There exists a logfile for each individual skin. The logging here is from the Skin's ResourceServlet.
Upon initialisation of the ResourceServlet there's a series of useful WARN statements written listing exactly
Default daily rotation.
An important part of SESAT is the logging functionality. All SESAT Kernel actions, choices, search results etc. are extensively logged for later parsing. An important part of SESAT future development is integration of statistics into the administrative portal.
Sesat's logfiles are written by Log4j and defined by sesat-kernel/war/src/main/conf/log4j.xml
The default configuration is daily rotation (sesam.access is the exception).
Two logfiles, sesam.marketing and sesam.sales, are not listed here as they are not yet in use.
SESAT produces several log files targeted to different users.
Default location of these logfiles is in your container's log directory.
This logfile contains the first log entry for all search requests, thus a good starting point for tracing a search request through the Search application. It partly mirrors the Apache access_log but splits the request up in two or three stages:
1. Initial log entry. This entry contains the actual http request parameters, in the <request>-element. Such as <url>, <http-referer>, <user> and <browser>.
2. Real-url. In case a pretty URL was submitted to the Search application, a second entry is logged. This time with a <real-url>-element.
3. Final log entry. Is logged after the search request has been handled by the Search application, when a response has been returned to the caller, and basically just list the http <response code="">.
Information to look for:
This logfile type is logged to when the Search application is through with the query server communication and knows how many hits the search got and which enrichment types should be returned. The following information can be read out:
Related to sesam.product but logs the underlying analysis scores for each query. Breaks the scores down to individual positive and negative hits for each predicate explicit in each analysis score.
This logfile type contains more technical information, such as a servlet's execution time and envoked search commands. The following data can be found:
Loggers involved in core initialisation of the engine, typically SiteKeyedFactories, also log to this file.
Read this log file for startup and configuration deserialisation errors.
This logfile has no supported format.
Logs a summary of every outbound http request made from sesat. This includes search commands, publishing fragments, and query evaluations.