About Crawling Module Logs

In this article

When you request help from the Coveo Support team for an issue with the Coveo On-Premises Crawling Module, you might be asked to provide your instance logs. These logs are located under C:\ProgramData\Coveo\Maestro\Logs (ProgramData is hidden by default), unless you changed this location. Each log file contains traces of Crawling Module activity and events, which can be helpful when troubleshooting unusual issues.

For each Crawling Module instance:

  • Crawlers logs contain information regarding content update requests that have been received from Coveo. Each of these log files is identified with a source ID that’s also displayed on the Sources (platform-eu | platform-au) page of the Coveo Administration Console.

  • Dumps are used by the Coveo Support team when investigating your issue, along with logs.

  • JobHandlers logs contain traces of the workers polling Coveo for update tasks. For example, these logs may be useful when you launch a refresh operation in the Coveo Administration Console, but the operation doesn’t appear to be processed by the Crawling Module.

  • Maestro logs are relevant when debugging issues affecting the Crawling Module as a whole, such as communication issues with Coveo, failure to start the workers, and inability to complete downloads.

  • Security-Provider logs contain information relative to security identity update requests that have been received from Coveo.

  • WorkerService logs, also known as NodeAgent logs, provide information on the worker launching process.

Component logs aren’t shared between Crawling Module instances. So, if you have more than one instance and encounter issues with a source, you must review the logs of the Crawling Module instance associated to this source. In other words, you must access the Logs folder on the server on which you deployed the Crawling Module instance with which this source is paired.