We will be undergoing scheduled maintenance on May 20th, 2013 at 02:00 GMT.
Microsoft Windows Server 2003 (70-290) Tutorials
Monitoring Server Performance / Logged Monitoring
Visitors to VTC.com will be able to view all introductory videos for each training course.
Free Trial Members will gain access to first three chapters for each training course.
Full Access Members have full access to VTC.com�s entire library of video tutorials.
Learn More
Subtitles of the Movie (Microsoft Windows Server 2003 (70-290) / Monitoring Server Performance / Logged Monitoring)
Where as real time monitoring gives us a snapshot view of the system at a particular point of time, logged monitoring allows us to build a baseline because it gives us a view of the activity of the system over a long period of time, over a period of weeks and perhaps in months. To do logged monitoring we don't use system monitor we use the performance console but instead of system monitor we use performance logs and alerts. So, if in the performance logs and the alerts tool we expand we see that we have three options. Counter logs, trace logs and alerts. We will talk about trace logs and alerts a little bit later on. Right now let us focus on counter logs. Now if I want to build a baseline counter log, we could right click on counter logs and then click on new log settings and then just type in the name, we just call it the baseline. Then I am going to press enter. Now I could add counters which would mean that I would be specifying certain counters for objects. But the nice thing about logs is that I can set the intervals so that it is not so much of a burden on the system. And therefore instead of just adding certain counters how to set the whole object and all of the counters to come with it?. So I am going to we click on add objects and then I am just going to pick them out what I want to know is I want to know about network interface and add, I want to know about memory and add, I want to know about physical disc and add, I want to know about processor, add and then click on close and we can see that then we have a baseline of information of all of these objects. We can then choose how often we want to sample data. Now by default its every 15 seconds but if I am going to do this over say a month then may be I don't need it every 15 seconds may be 15 minutes would be just fine. That is much less of a load on the system. Now if I wanted to run it as a particular user as a particular account we can set that it as well. Right now we are not even going to worry about that. Now if we click on schedule then we can schedule when we want this to start and when we want it to stop. So if I said I want to manually start the log and I want to manually stop the log then I am responsible for starting and stopping it. On the other hand we can set the timer at which it will start. In this case I am going to manually start the log and then I going to click on ok. Now the baseline log has been created and whenever I want to start the log I just right click on the baseline log and then click start, it is as simple as that. Now when I want to stop the log I can stop the log or as we said I can set the log to run for a certain period of time. I can set it to start on a certain day and then let me know when it stops. As you can see being able to create these logs they gather this information over a long period of time. It is great tool for the network administrator and you should know the difference between just taking a look at the snapshot and using the system monitor tool, and taking a look at the counter log or creating a counter log and using the performance logs and alerts tool for that. We can also create trace logs. Now the biggest difference between a trace log and a counter log is that a trace log only gives me information if certain things happen. For example I want to create a new trace log. So let us say new log settings and then we just call this tracelog2, we already have one trace log, click on ok and tracelog2 then is going to ask me, ok what do you want to look for? Events log what the system provides, process creations and deletions thread creation and deletions and we check what we going to look for, and depending on what we check some of these are more intense on the system, more intensive on the resources of the system than other, For example if we check page faults the system warns us because collecting page faults data consumes a significant amount of resources. So we can determine what we want to set for trace logs. But the biggest difference between a trace log and a counter log is that a trace log only gives us information if certain things happen, where as a counter log just starts tracking those objects that we have set. So we can create counter logs and we can create trace logs but we can also set the system to alert us when certain thresholds are met also and we will take a look at alerts in our next section.
Tutorial Information
| Course: | Microsoft Windows Server 2003 (70-290) |
| Author: | Bill Ferguson/Certified Instructor |
| SKU: | 33497 |
| ISBN: | 1932072918 |
| Release Date: | 2004-06-03 |
| Duration: | 8.5 hrs / 107 lessons |
| Captions: | No |
| Compatibility: |
Vista/XP/2000, OS X, Linux QuickTime 7, Flash 8 |
VTC Sign up & Benefits
- Unlimited Access
- 81,350 Video Tutorials (14,200 free)
- Video Available as Flash or QuickTime
- Over 715 Courses
- $30 for One Month Access
- Multi-User Discounts Available
