How to Create a Performance Monitor Log for NT Troubleshooting

Last reviewed: March 19, 1998
Article ID: Q150934
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.5, 3.51, and 4.0
  • Microsoft Windows NT Server versions 3.5, 3.51, and 4.0

SUMMARY

This article explains how to create a Performance Monitor log so that engineers can use it to troubleshoot performance problems on a computer running Windows NT.

MORE INFORMATION

Creating the Performance Monitor log:

  1. On the View menu, select Log.

  2. On the Edit menu, select Add To Log

  3. In the Add To Log dialog box you will see Computer and Objects. In Computer, specify the name of the local computer or a remote computer you want to get a log of. In Objects, add the counters that you want Performance Monitor to log. These counters will change depending on the problem that you are troubleshooting.

  4. Highlight the objects that you wish to monitor and select Add.

  5. Under Options select Log.

  6. Under File Name, name the log.

  7. At the bottom of this window you will see Update Time. It is important to set this update time. If you are going to be running the Performance Monitor log for an extended period of time, you will want to set this update time to an interval much higher than 15 seconds or the log will be very large. If you are only going to be running the log for an hour then 15 seconds will be fine.

  8. Now you are ready to start the log. Press the Start Log button located in the same window as the above. This will start the log and this icon will change to a Stop Log icon once the log is started.

When you are ready to stop monitoring the selected objects and examine your log file perform the following steps:

  1. Under Options select Log and Stop Log.

  2. Under the Options menu select "Data from" and "Log File". Now

        select the radio button beside the perfmon.log field and locate
        your log file.  Choosing File and Open cannot open a log file.
    

  3. After opening the log file, add the objects and counters that were

        monitored.  Do this for each view needed otherwise the log file's
        data will not be available.
    

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:

   Memory
   Paging File
   Process
   Processor
   Server
   System

NOTE:
  • If the computer is restarted or goes down while the log is going, you can start a new log, or if you specify the name of an existing log file the new data is appended to the end of the log file. It is important to let the engineer know the log was restarted.
  • If there are processes that start after the log was started they will not show up in the beginning of the log. You will need to go to Edit and select Time Window. There is a sliding scale that you can use to view different periods in the log.
  • If the user logs off, the performance monitor log will stop. Performance logging can be setup as a service but running Performance Monitor remotely from another Windows NT system is the easiest way to collect a performance log.


Additional query words: prodnt perfmon tshoot
Keywords : NTSrvWkst
Version : WinNT:3.5,3.51,4.0
Platform : winnt
Issue type : kbtshoot


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 19, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.