SharePoint is an extremely complex system that contains a lot of sub-modules, and if each submodule has its own log hit out words, then the log the growth will be very fast and will consume a lot of disk space.
Therefore, the system in normal operation, do not need to open all the log, only when the specific module problems, it is necessary to play a detailed tracking log.
into the SharePoint Central Administration, locate the Configure diagnostic log:
here SharePoint Lists all the sub-modules that can set the log level:
Expand the Sub-module, you can see again the function of subdivision, take SharePoint Server For example, each of these features is listed below, and you can see that the default is Information level of logging.
Select the module you want to find, and then adjust the log level below:
The first is to say which logs to write to Windows in the System log, the second one says, which logs are written to SharePoint in the log.
From top to bottom is in order from the most urgent to the least urgent, so to get all the logs, you have to choose the bottom.
when a detailed tracking log is turned on, the log is a fast-growing issue. To protect your system,SharePoint provides a number of protection measures.
one is to protect Windows The system log should not be too large. If the following option is checked, the repeated events are automatically acquired and compressed.
and for SharePoint log, you can set the number of days to save by default - days. If you think that the log is still very large, you can also limit log to occupy the maximum space, after this volume, the previous Log will be automatically clear.
turn on tracking Log after that, you can find more information to diagnose SharePoint problems that arise. But be sure to remember that after the completion of the diagnostic process, be sure to change the settings back, so as not to generate a large number of logs.
Monitor SharePoint Efficiency (iii) – Turn on the trace log