About Component Logs

When you request assistance from the Coveo Support team for an issue with the Coveo On-Premises Crawling Module, you might be asked to provide the logs of some Crawling Module components. These logs are located under C:\ProgramData\Coveo\data\Logs, unless you changed this location (see Moving the Data Directory). Each log file contains traces of Crawling Module activity and events, which can be helpful when troubleshooting unusual issues.

The Crawling Module logs several types of data in different files. In particular, the following are often requested by the Coveo Support team:

  • Maestro logs are relevant when debugging issues affecting the Crawling Module as a whole, such as communication issues with the Coveo Cloud platform, failure to start the workers, and inability to complete downloads. This file also includes information on worker updates.
  • Updater logs contain data regarding Maestro updates.
  • Under Crawlers\Log, the Crawlers_log4net logs contain information regarding content update requests that have been received from the Coveo Cloud platform. Each of these log files is identified with a source ID that is also displayed in the Sources page of the Coveo Cloud administration console (see Adding and Managing Sources).
  • Under Crawlers\Log, the JobHandler logs contain traces of the workers polling the Coveo Cloud platform for update tasks. For instance, these logs may be useful when you launch a refresh operation in the Coveo Cloud administration console, but the operation does not appear to be processed by the Crawling Module.
  • Under Crawlers\Log, the Crawlers_PlatformLogger logs contain information regarding each item made searchable by Coveo Cloud. A worker ID identifies each log.