A DCS can contain any number of data collectors, allowing for greater control over performance monitoring and data organization tasks.
DCSs have been implemented to provide support for performance reports that require data from multiple log files of different types. These data collectors include counter, trace, alerts, and system configuration logs. You can add any number of data collectors to a single DCS. While you can use Performance Monitor right out of the box, so to speak, I've discovered that creating a customized version via the Microsoft Management Console MMC provides a more focused approach to any monitoring operation.
Plus, creating a customized console for a specific task has other benefits. To begin with, you can quickly and easily use the monitoring tool at any time. And best of all, you can copy the customized console to a CD and use it on other systems.
Fortunately, creating a customized console is easy. To begin, access the Run dialog box from the Start menu and type mmc in the Open text box. When you see the empty console, pull down the File menu, select the Save command, name the console Memory Tracker.
Only this time through, you'll name the control Log Viewer. Once you've created your custom Memory Tracker console, you're ready to add the counters that will allow you to track memory usage. To begin, maximize the window, select the Memory Counters icon, and then click the Add button on the Performance Monitor toolbar that appears in the right panel.
Alternatively, you can press [Ctrl]-I. When you see the Add Counters dialog box, you'll use this data to add the necessary counters to the graph:. Select an object from the Performance Object drop-down list and then select the associated counters from the scrolling counters list.
As you select each counter, click the Add button. As you do so, you'll see that counter appear in the graph and in the legend below the graph. I'll discuss these counters in more detail later when I explain how to interpret the results of the monitoring operation.
For now, just keep in mind that the reason I selected counters from these particular Performance Object categories is that when combined, they provide an excellent picture of how Windows XP is utilizing its memory potential during a typical computing session.
By memory potential, I'm talking about both physical and virtual memory. To continue, click the Close button to dismiss the Add Counters dialog box. At this point, you're ready to configure the monitoring operation. As soon as you return to the Memory Tracker, you'll see that it's already charting your memory usage in the graph area. As you'll notice, the timer bar will be running very quickly.
That's because, by default, the sampling interval is set at 1 second and the graph is set to use a default time period, called the Duration, of 1 minute 40 seconds. As such, you'll want to change the sampling interval, which will in turn extend the Duration. To do so, click the Properties button on the toolbar. When you see the System Monitor Properties dialog box, locate the Seconds text box on the General tab and change the value to something more appropriate.
To get a good picture of memory usage, I suggest that you select a sampling interval of 15 seconds. While this may sound like an odd interval, there is a method to my madness, and that is that this interval extends the Duration of the data collection to exactly 25 minutes. If you wish to extend the monitoring operation to a longer time period, you can set the time interval to seconds.
Doing so will set the Duration to exactly one hour. You're now ready to start your monitoring operation. 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.
On the General tab in Windows ,click Add to add the counters 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.
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.
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:. 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:. 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.
You can start the log on an event using Performance Logs and Alerts.
0コメント