Logging is one of the most important functions in SharePoint for
diagnosing problems. Users can configure log settings in SharePoint 2010
Central Administration site.
To open the Diagnostic Logging page, go to CA->Monitoring->Configure diagnostic logging.
1.
Expand any relevant submenus and then select one or more categories of
events for which to configure throttling. Throttling controls what
events are captured in the Windows events log according to the
criticality of the events.
2. After you select the types of events to throttle, perform one of the following actions:
a. Expand the Least critical event to report to the event log menu and then select the type of event that you consider to be least critical for the event log.
Note: Events that are equally critical to or more critical than the selected event will be recorded in the Windows event log. The list entries are sorted in most-critical-to-least-critical order.
b. Expand the Least critical event to report to the trace log menu and then select the event type that you consider to be the least critical for the trace log.
Note: Events that are equally critical to or more critical than the selected event will be recorded in the trace log. The list entries are sorted in most-critical-to-least-critical order.
1. You can type the path to the folder in which trace logs will be saved.
Note: The location you specify must exist on all servers in the farm.
2. In the Number of days to store log files box, you can set the maximum number of days?that a trace log file is saved.
3. Select the Restrict Trace Log disk space usage check box to monitor and limit the amount of storage space used by trace logs.
Note: In the Maximum storage space for Trace Logs (GB) box, you can type the maximum number of gigabytes (GB) allowed for storage of trace logs.
To open the Diagnostic Logging page, go to CA->Monitoring->Configure diagnostic logging.
I. Event Throttling
Users can control the severity of events captured in the Windows event log and the trace logs with these settings.
1.
Expand any relevant submenus and then select one or more categories of
events for which to configure throttling. Throttling controls what
events are captured in the Windows events log according to the
criticality of the events.2. After you select the types of events to throttle, perform one of the following actions:
a. Expand the Least critical event to report to the event log menu and then select the type of event that you consider to be least critical for the event log.
Note: Events that are equally critical to or more critical than the selected event will be recorded in the Windows event log. The list entries are sorted in most-critical-to-least-critical order.
b. Expand the Least critical event to report to the trace log menu and then select the event type that you consider to be the least critical for the trace log.
Note: Events that are equally critical to or more critical than the selected event will be recorded in the trace log. The list entries are sorted in most-critical-to-least-critical order.
II. Event Log Flood Protection
Select the “Enable Event Log Flood Protection” check box, if you want to detect and suppress repeating events.
III. Trace Logs
When tracing is enabled you may want the trace log to go to a certain location.1. You can type the path to the folder in which trace logs will be saved.
Note: The location you specify must exist on all servers in the farm.
2. In the Number of days to store log files box, you can set the maximum number of days?that a trace log file is saved.
3. Select the Restrict Trace Log disk space usage check box to monitor and limit the amount of storage space used by trace logs.
Note: In the Maximum storage space for Trace Logs (GB) box, you can type the maximum number of gigabytes (GB) allowed for storage of trace logs.
No comments:
Post a Comment