You can change the default logging configuration of the Endeca IAS
Service and any IAS components you run from the command line.
Log location and rolling
IAS writes log files to the
<install path>\IAS\workspace\logs directory.
If desired, you can reconfigure IAS to write log files to another location.
IAS rolls a log file once it exceeds 100MB, and the IAS Service keeps
10 backups of its log.
Note: If you delete the log file, the Endeca IAS Service recreates the
log only when you restart the service. So it is possible to delete the log, run
a crawl, and not have logging information if you did not restart the service.
Configuration files for IAS components
The
<install path>\IAS\workspace\conf directory
contains the following logging configuration files:
- ias-cmd.log4j.properties
- configures logging for the IAS Server Command-line Utility
- ias-service-log4j.properties
- configures logging for the Endeca IAS Service
- component-manager-cmd.log4j.properties
- configures logging for the Component Instance Manager Command-line Utility
- recordstore-cmd.log4j.properties
- configures logging for the Record Store Command-line Utility
Logging options and levels
You can reconfigure log locations, log file size, log file encoding,
log pattern, and logging message levels.
Logging levels can be set to any of the following:
- DEBUG
designates fine-grained informational events that are most useful to debug
Record Store problems.
- INFO designates
informational messages that highlight the progress of Record Store operations
at a coarse-grained level.
- WARN designates
potentially harmful situations.
- ERROR
designates error events that might still allow the Record Store to continue
running.
- FATAL
designates very severe error events that will presumably lead the Record Store
to abort.
- OFF
has the highest possible rank and is intended to turn off logging.
These levels allow you to monitor events of interest at the
appropriate granularity. When you are initially setting up your Record Store
implementation, you might want to use the
DEBUG level to get all messages, and change to a
less verbose level in production.
Log file encoding
IAS produces log files encoded as UTF-8.
