Configuring logging

This section describes how to configure logging for CAS.

Configuring logging for CAS components and command-line utilities
You can change the default logging configuration of the Endeca CAS Service and any CAS components you run from the command line.
Setting log properties for troubleshooting CMS connector issues
You can set logging properties that may help determine the causes of connection, authentication, and request/response time issues between the CAS and the CMS provider.
Excluding failed records from the CAS Service log file
If a record fails during a crawl, the CAS Server discards the failed record and writes a truncated version of the record to the cas-service.log file. If you do not want the CAS Server to write any information about failed records to the log file, you can disable logging for failed records by uncommenting a setting in the cas-service-log4j.properties file.
Enabling log timing information for crawl processing steps
You can enable a logging setting in cas-service-log4j.properties that instructs CAS to write log timing information for each processing step of a crawl. This additional logging information is especially useful for troubleshooting performance issues.
Examining the Endeca CAS Service log
The Endeca CAS Service logs messages for all CAS components and crawls in the cas-service.log file.