Configuring Diagnostics Logging on a ServerDiagnostics logging levels determine which additional Exchange events are written to the Application event log in Event Viewer, a Microsoft® Windows Server™ 2003 component that you can use to monitor hardware and software activities. You can use diagnostics logging to record significant events that are related to authentication, connections, and user actions. The first step in configuring diagnostics logging is to decide which services on an Exchange server must be enabled for diagnostics logging. Note You configure diagnostics logging separately for each service on each server. For example, if you enable protocol logging on an individual virtual server, it is the setting on the Exchange server on which the virtual server runs that determines the logging capabilities for the protocol.
After selecting a service, the next step is to set the logging levels for those services. There are four logging levels of detail. When Exchange generates an event less than or equal to the logging level, the event is logged. Events range from significant events (such as application failures) to moderately important events (such as the receipt of messages across a gateway) to events that are relevant only to debugging. Typically, you log only critical events. However, when problems occur, diagnostics logging helps you to change the logging levels to capture more events in greater detail.
After selecting a logging level, logging begins automatically whenever you start Exchange. You can view the log entries in Event Viewer. For more information about configuring diagnostics logging, see How to Configure Diagnostics Logging. |