All ELOxc log files can be found in the file directory, which is configured in the parameter "LogDir" of ELOxc.xml. This parameter is read when the service starts to ensure that you get the maximum available analysis options. The service log that correlates with the Windows service is written to this directory. It logs important initializations and service requests, and each configured instance has its own instance with the same name. The _Replies directory contains only those service calls that do not address an instance and are usually transmitted via the Web API.

The log directory of the instance only contains the update logs that are created when a user switches to a different version. Otherwise, it only contains child directories that correlate with the timestamp of the original service. The logs for the respective instance are below these. In addition, the log directory of the instance contains a child folder named _Replies, which contains all function calls processed in the instance. These calls are also usually transmitted via the Web API.

The main log directory of the instance contains the logs "Main" and "Catalog". "Main" logs when the configuration is processed, whereas "Catalog" logs the results of the initial catalog requests. Individual jobs within an instance are written to a separate child directory each time a job starts.

An ELOxc job writes the catalog requests made when a job starts to a file named "JobCatalog". The element selections are written to a file named "JobControl" in the job's main log. Processing errors are written to "JobErrors" and processing details are written to "Worker". Once a job has finished, the job's child directory is written to a ZIP file and then deleted.

The "LogAge" parameter in ELOxc.xml configures the retention period for logs. The default value 0 ignores the log age. Other values, i.e. greater than 0, are interpreted as the maximum log age in days up to a maximum of 365. Once logs reach the configured maximum age, they are automatically deleted.

Please note: If automatic deletion of old logs is enabled, you must ensure that you set an appropriate value for the parameter "LogDir". The delete routine deletes all files in the configured log directory, regardless of whether they are actually logs or not.