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.

To exclude failed records from the CAS Service log file:

  1. Stop the Endeca CAS Service.
  2. Navigate to the CAS\workspace\conf directory.
  3. In a text editor, open cas-service-log4j.properties.
  4. Uncomment the line containing the log4j.logger.com.endeca.itl.executor.ErrorChannelImpl setting.
  5. Save and close the cas-service-log4j.properties file.
  6. Start the Endeca CAS Service.

Once you uncomment the setting, the CAS Server does not write any information about failed records to the log file. However, failed records are still counted as metrics under FAILED_RECORDS.