Your disk savings won’t be crazy big, but every little bit counts. There is another way to do it by using PowerShell . Also make sure that same location is available on all the servers of the farm. You can even use it as external Figure 2. It is recommended to have the SharePoint logging database  database Microsoft added more logging and debugging capabilities to SharePoint 2010 to help developers include additional monitoring and troubleshooting to their custom applications. SharePoint 2010 improves on this task of finding specific log entries by assigning some uniqueness to each log entry. Next you need to specify the log file location and maximum size of the log file Liked this article? The following example shows how to add a new class to a non-sandboxed solution and have the class inherit from the SPDiagnosticsServiceBase class. Note: The location you specify must exist on all servers in the farm. to some other drive than the drive on which SharePoint has been installed (and Another change Microsoft introduced is a new database that contains all logging information for all servers in the farm. By default it is stored in a log folder of the "14 Hive" I run other ULSLOGVIEWER.EXE as well to see but i could not find it.. One transistor square wave amplifier: why doesn't it work? SharePoint Log Viewer is very efficient and has a lot of options like view real-time logs, export logs, show logs from multiple files, filter based on various filter columns. TK, great post, I always move the logs (including the IIS Logs) and the Search Index. all the related log entries together. It only takes a minute to sign up.

Troubleshooting with trace files is good but wouldn't it be Health Logging Schedule by clicking on either of these links. Using just a few lines of code you can log information from your custom components: You can sort, filter, and analyze this data to determine who has done what with sites, lists, libraries, content types, list items, and library files in the site collection. to connect to the database for logging. I am analyzing the SharePoint 2010 traffic for my site , I got confuses when I analyzed the IIS logs and SharePoint Web Analytics results, because the result is quite different, Like:

By default, the Developer Dashboard is not turned on. IIS logs are particularly useful when you need to do a capacity review of your WFEs. The capturing of usage and health data collection is enabled by default. First ,create a new application page that will serve the purpose of the custom system application page. I am analyzing the SharePoint 2010 traffic for my site , I got confuses when I analyzed the IIS logs and SharePoint Web Analytics results, because the result is quite different, Like: Top Pages of SharePoint's web Analytics is 228 (for last 6 months), while on the other side IIS log shows 47,442 (for last 6 months). The best applications contain a good measure of logging to assist developers in tracking down errors when things do not go as they were designed or when unexpected things occur. This centralized consolidation of data, from all servers helps you to better generate reports for analysis purposes and troubleshooting. The cmdlet is Set-SPDiagnosticConfig and the parameter is –LogLocation. Also make sure that the same location is available on all the servers of the
called CorrelationId about which I talked in my This article walks through some common logging and debugging techniques that are now available to developers when building SharePoint 2010 solutions. Normally this would be simple, but auditing was turned off within Sharepoint up until now. Thanks for contributing an answer to SharePoint Stack Exchange! Great post Todd. What is meant by "ground truth" in the context AI? One reason for this is so users do not see unfriendly errors, and instead are presented with a more graceful error page.