ULS Active best practices report by SPDocKit determines whether there is an issue with the Unified Logging Service (ULS) configuration.
This check determines whether there is an issue with the Unified Logging Service (ULS) configuration. If the log file growth is not restricted, it may lead to issues.
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.
The ULS logs the information to two locations: the Windows Application Log and the Trace Log. By default, the Windows Application Log will contain a much less information than the trace log. The Windows Application Log is also usually configured to overwrite the log file once it reaches a certain size.
On the other hand, the trace log is written to the text file on the file system, and it 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 the trace log can have a massive performance effect on the file system. In addition, the log files can take up a lot of disk space.
When the ULS is working correctly, the diagnostic logging directory should be regularly updated with new data at least every 24 hours. If this is not the case, verify that the SharePoint Tracing Service account is a member of the local Performance Log Users group. You can use Services and Local Users and Groups MMC snap in. Also, check for the correct trace log location under Central Administration > Monitoring > Reporting > Configure diagnostic logging. It is available under Trace Log > Path.
Additional information can be found in the following article: