Summary
This article describes how to create log files using System Monitor in Microsoft Windows 2000, Microsoft Windows XP or Microsoft Windows Server 2003.Download and use the Performance Monitor Wizard (PerfWiz) to make the log configuration process easier to set up.
More Information
The System Monitor tool included with Windows 2000, Windows XP and Windows Server 2003 is the administrative tool that replaces the Performance Monitor tool included with Windows NT 4.0. Here is a list of some improvements in the System Monitor tool:
-
You can log specific counters and instances of an object, which helps you reduce the size of log files.
-
The Print Queue object is a new Performance object that allows you to monitor aspects of a print queue.
-
You can start the log on an event using Performance Logs and Alerts.
-
Other Performance objects have also been added.
-
A sample log file is included in Windows 2000.
To create a new log:
-
Right-click Counter Logs, click New Log Settings, type a name for the log, and then click OK.
-
On the General tab in Windows 2000,click Add to add the counters you want. On the General tab in Windows XP or Windows Server 2003, click Add Counters.
-
On the Log Files tab, click the logging options you want.
-
On the Schedule tab, click the scheduling options you want.
You can set similar options in Alerts. For example, you can configure the alert to send a message, start a performance data log, or run a program, if a counter exceeds a certain value.
Using Performance Monitor Wizard
To obtain and download the Performance Monitor Wizard (PerfWiz). The Performance Monitor Wizard simplifies the gathering of performance monitor logs. It configures the correct counters to collect sample intervals and log file sizes. This wizard can create logs for troubleshooting operating system or Exchange server performance issues. NOTES:
-
If you are troubleshooting a performance issue or an issue that looks like a memory leak, the objects that Performance Monitor should log include but are not limited to the following items. Memory resource issues:
Cache Memory Objects Paging file Process Processor System Terminal Services (if a Terminal Server) For all other resource issues, add additional counters:
Logical disk NBT Connections Network interface Physical disk Redirector Server Server work queues Thread (do NOT capture if a terminal server) All Terminal Server counters (if a Terminal Server) All Protocol counters bound to network adapters
-
Physical Disk counters are present by default on Windows 2000.
For additional information about how to view log files for memory leaks and performance bottlenecks, click the following article number to view the article in the Microsoft Knowledge Base:
150934 How to create a Performance Monitor log for NT troubleshooting Also see Determining acceptable values for counters under Performance counters in Windows 2000 Help.
