Performance Logs and Alerts is the primary tool by which you can create baselines, document activity, and also track objects and counters over a period of time. The purpose behind creating baselines and tracking data over a period of time is to perform what’s known as trend analysis, which is basically the concept of gathering enough information to be able to point out specific patterns in the data that point to real actions that are going on elsewhere on the system.
An example might be if you found that processor queue lengths increased every day around 8am, then you might conclude that the logon traffic generated over the network might be taxing the CPU. Rather than purchasing an additional CPU, you can modify server and domain configurations in such a manner as to perhaps offload some or the entire login processing to another system, and thereby relieve the stress on the CPU. Again, if the current CPU queues at 8am do not exceed the norm CPU queues at that time, you’ll need to look further and deeper for the culprit(s).
The Performance Logs and Alerts section is divided into three subsections: Counter Logs, Trace Logs, and Alerts. Counter Logs are the logging equivalent of what you see within System Monitor. Right-clicking on an empty section of the right pane will enable you to create a new log and subsequently define the logfile, its output type (text, binary, etc), and the objects/counters that the log will maintain. Again, objects are the equivalent of major systems or hardware on the server. Counters track specific events related to a given object. You have the option for choosing all counters within a single object, or choosing multiple counters that belong to separate objects. The purpose again, is to enable you to track only the information that has the impact that you are searching for.
[tags]performance log, XP Pro, baseline, track object, queue[/tags]