Diagnostic Log Path
Diagnostic Log Path best practices report by SPDocKit determines whether the SharePoint Log Files are stored on the primary drive.
Last updated
Diagnostic Log Path best practices report by SPDocKit determines whether the SharePoint Log Files are stored on the primary drive.
Last updated
This check determines whether the SharePoint Log Files are stored on the primary drive.
SharePoint utilizes Unified Logging Service (ULS) logs to log events within SharePoint. These logs can be used to troubleshoot configuration and infrastructure issues and to find issues in the custom code by exposing debugging information.
ULS logs the information to two locations: Windows Application Log and Trace Log. By default, a Windows Application Log will contain much less information than a trace log. The Windows Application Log is also usually configured in such a manner that it overwrites the log file once it reaches a certain size.
A trace log, on the other hand, is written to a text file on the file system and contains much more information than the Windows Application Log. Default location is C:/Program Files/Common Files/Microsoft Shared/Web Server Extensions//LOGS. Depending on the number of users accessing the system and the logging level configured, writing to trace log can have a massive performance impact on the file system. Therefore, it is highly recommended that trace logs be stored on a dedicated drive.
Make sure that ULS trace log files are not stored on the same drive as the primary (system) drive or the paging file. To do so, go to the Central Administration > Monitoring > Reporting > Configure diagnostic logging. You can use this page to configure logging level and trace log settings. Specify a new location under Trace Log > Path and click OK.
Please note that this is a farm-wide setting. This means that the path you specify here must be physically available and accessible to each SharePoint server in your farm.
Additional information can be found in the following article:
