This is to remind the user that a logging session is currently underway and will continue to grow in size until the user stops the collection process. Your log file is now ready for immediate analysis in the chart mode. To obtain the greatest benefit, you should log several objects on a particular system, depending on what application is running and what subsystems are involved in moving and processing data. For example, Web server applications tend to stress processor and network resources, but not memory or disk resources. Database applications tend to stress processor, memory, and disk resources, but rarely network resources.
Messaging applications tend to stress all of the above.
You should begin in log mode by monitoring more objects rather than less, at least until you have deemed that particular subsystems are not at risk for potential performance issues. After capturing the right data by logging the appropriate objects on a particular system, you can move to the analysis stage. To help narrow your area of focus, you should analyze the counters of a single object. Because Perfmon was written with hardware and software subsystems in mind, it is logically organized to lend itself to views and presentations sorted by subsystem type. These counters are all related to hardware and software system-level resources.