Global options include log file options and real-time options:

Log file options specify the size of the log file and how logs are maintained:
- Maximum size. This is the maximum size for all individual log files.
- Circular logging. Use this option to specify whether Logging Tool resumes writing entries at the beginning of the file, after the log file reaches the maximum file size.
- Sequential logging. Use this option to specify whether Logging Tool stops logging operations, after the log file reaches the maximum file size.
- New file. Use this option to specify whether logging is to roll over the log file and start over, after the file reaches the maximum size. This generates a new log file.
Real-time options specify how logging performs in real-time monitoring and filtering:
- Real Time Monitoring. Use this option to see traces in the console window as they accumulate. You can also use the Display only, no log fileoption with real-time monitoring, which enables you to see traces in the console window, but does not generate a log file.
- Filter Options. You can use the Enable Filtersoption to enable filtering on log files so that only traffic to and from the addresses you specify are displayed. You can specify URI addresses, which will include only traffic to and from the specified SIP URI in the log file, and FQDN addresses, which will include only traffic to and from the specified computer FQDN in the log file. Trace filtering for URIs and FQDNs is available only for the SipStack and UserServices components; for all other components, the traces cannot be filtered at run time.

Note:
Although it can be useful to continue logging for a day or more to help troubleshoot an intermittent problem, we recommend that you not run real-time monitoring for more than an hour at a time. We also recommend that you not use Logger Tool for ongoing monitoring. Turning on logging for an extended time for servers in a production environment can affect server performance. For details about monitoring and troubleshooting, see the Office Communications Server 2007 R2 documentation at http://go.microsoft.com/fwlink/?LinkID=132106 .

Note:

Although it can be useful to continue logging for a day or more to help troubleshoot an intermittent problem, we recommend that you not run real-time monitoring for more than an hour at a time.

We also recommend that you not use Logger Tool for ongoing monitoring. Turning on logging for an extended time for servers in a production environment can affect server performance.

For details about monitoring and troubleshooting, see the Office Communications Server 2007 R2 documentation at http://go.microsoft.com/fwlink/?LinkID=132106 .

To specify global options

Open Office Communications Server 2007 R2 Logging Tool, New Debug Session.
Under Global Options, do the following:
- Under Log File, in Type, click the type of log file you want to use.
- To enable real-time monitoring, select the Real Time Monitoringcheck box and, if appropriate, the Display only, no log filecheck box.
- To configure filters for real-time monitoring, under Filter Options, select the Enable Filterscheck box, and then specify URI and FQDN addresses to and from which you want to enable filters.