Mike Skutta Blog

Sitecore How-To: Enable Verbose Logging for Sitecore Content Search

Erik Carron and Mike Skutta


This is an article in a series of Sitecore how-to articles. These articles are meant to be quick guides to accomplish various tasks within Sitecore. The how-to articles have proven to be very helpful internally at One North Interactive https://www.onenorth.com. These articles assume working Sitecore knowledge. I just wanted to share the articles with the community. Hopefully you find them helpful.


When debugging index crawling and searching, it may be helpful to enable verbose logging.

Enabling this will generate a lot of logging. I would not suggest enabling this if you have a lot of content to index. If you are debugging index rebuilds, I suggest limiting the amount of content that is indexed.

Step-by-step guide

  1. Drop the following file into the Website\App_Config\Include\zzz folder:
     <?xml version="1.0" encoding="utf-8" ?>
     <configuration xmlns:patch="http://www.sitecore.net/xmlconfig/" xmlns:set="http://www.sitecore.net/xmlconfig/set/" >
           <!--  VERBOSE LOGGING
                 This feature is designed to facilitate search index configuration and provide the necessary insight
                 in troubleshooting scenarios. For example, if a particular item is not getting indexed,
                 the VerboseLogger can provide more context and help you to figure out the problem.
                 It is important that you only enable the VerboseLogger component in special circumstances
                 and never run it for long periods in a production environment.
                 Otherwise, this would result in an extremely large log file, which may have performance implications.
           <setting name="ContentSearch.VerboseLogging" set:value="true" />
           <logger name="Sitecore.Diagnostics.Search">
             <!-- <level set:value="DEBUG"/> -->
           <logger name="Sitecore.Diagnostics.Crawling">
             <!-- <level set:value="DEBUG"/> -->
  2. Uncomment the log4net changes depending on what you are debugging.
  3. View the Crawling.log.* and Search.log.* files.

Similar Posts