This post was most recently updated on December 11th, 2018
Introduction to Performance Monitor Logs
Creating and interpreting logs is the key to monitoring your Windows 2003 servers and network performance.? The logs are the central blank in your strategy to discover and remove bottlenecks from your system.? This page concentrates on creating a log of your server”s activity, however there are other tactics, for example, creating Alerts.
Our first mission is to collect data about your server”s memory, processor, disks and network.? In addition to monitoring the Windows Server operating system, we often need to collect SQL and Exchange counters.? The benefit of creating a log is that we can analyse hours of performance at leisure.? The alternative of constantly watching the System Monitor soon wears off.
Another advantage of studying logs rather than viewing System Monitor is that you can use logs to track trends.? If necessary, you can go back months to confirm a change in resource usage.? Moreover, if you keep old logs then you can see precisely when a problem originated.
Performance Log Topics
?
Performance Monitor Logs
Whilst this page will show you how to create logs with Performance Monitor, it does assume that you are familiar with Windows 2003”s System Monitor interface. (See here for a refresher)
Creating your first logThe performance monitor log, holds all the counters of all the objects and that you wish to track.? The advantages of a log over the System Monitor is that the log captures the data permanently in an actual file.
Logman For those who like the command prompt, there is a utility called: logman.? Personally, I find the syntax too difficult for regular use, but I agree with ”Mad” Mick, you can use logman in batch files. |
Diagram 1 (Above) Diagram 2 (Above) |
|
Viewing your logTrust me!? Have faith that your performance monitor log has collected reams of data.? I say this because every time I examine a log, for a split second I think, ”It”s empty”. ?
? |
Diagram 3 (above) ? |
Save Settings As?To re-use your counters for future logging, right click the counter in the Performance Monitor console, then select Save Settings As; note the .htm format.? As a bonus, you can now open the file in Internet Explorer and track the System Monitor.? I guess everything is web based these days. Log FormatsText File: – Tab or Comma Delimited.? Best for 95% of all counter logs. Binary: – Useful for intermittent data. SQL Database:? You need the name of an existing SQL database.? Used for recording lots of data about lots of servers, the enterprise scenario. The next step – Schedule those logsCreate a schedule so that logs start automatically early in the morning, and run thought the day until everyone has gone home.? In fact, you may want to run the log for the full 24 hrs, I once used a log to un-earth a problem caused by backup in the middle of the night. You may wish to run a test log for 10 minutes and check how big it gets, then multiply up by how many hours you wish to run the log.? As a result of your test, you may want to move the log to a folder on a partition with more free space. To configure a schedule, right click your counter log, properties, Schedule Tab. Summary of First LogWith a little guidance you will soon be able to create Performance Logs for your Windows 2003 servers.? Once you learn the technique and understand the menu items, you will soon be creating logs to check for bottlenecks on your network. |