After all the preconfigurations, installations, and setting up of virtual machines, everything is up and running normally. However, what you really need to consider is what is normal. What is the regular performance and system utilization for your physical and virtual servers?
Logged monitoring will help you to answer the question, measure realistic conditions, and identify the needs of servers and hardware upgrades, optimization, and tunings using trend analysis. This is an example of what you can get using baselines. A baseline is the level of system performance that you decide is acceptable. Normally, they are decided before deployment during the planning phases.
Using data collector sets from Perfmon, you can get realistic and advanced trend information and create baselines that can start and stop automatically based on your schedule.
This recipe will show you how to use Perfmon to create baselines for your physical and virtual machines.
Baselines must track the server activities during a specific period of time. You can create daily, weekly, monthly, or any other schedule you need. Before you start, decide what you want to monitor, such as processor, memory, disk, and network, and also for how long it will be monitored.
The following steps will show you the default system data collector sets and how to create user-defined collector sets:
performance monitor
and press Enter.On Windows Server, Perfmon is the only built-in tool that can be used for logged monitoring. It comes with two system-collector sets that can be used to get advanced reports showing system diagnostics and system performance.
Under User Defined
, you can create your own collector sets, based on the application or the hardware you want to monitor.
For virtual environments, you can only use the host partition to analyze all the performance trends, but in some exceptions, a monitoring method, within particular virtual machines, is required.
Hyper-V has specific counters that let you know everything that is happening in the virtualization stack, virtual machines, and host resources. Some counters also have instances that can be triggered to monitor something more specific. For example, when the Logical Disk counter is being used, you can select which disk (instance) you want to add.
Due to a high number of counters, the following list shows only a small selection of Hyper-V counters based on the subsystem that will be monitored. They can be used in conjunction to also monitor parent and child partitions.
There is no standard for creating a baseline; each environment is different from the other. You will need to identify which resources need to be monitored and then create your own monitoring plan. The number of counters being monitored and the duration is also very important. If you have a data collector set with lots of counters, which uses small intervals of time, you might experience performance, storage, and network issues. Make sure the interval used is larger for longer monitoring windows. For instance, to monitor a server for one day, you can use a 10-minute interval and for one week of monitoring, a 1-hour interval.
In case you don't have a plan and just want to run a baseline to track and analyze your system growth, you can create four baselines using the counters from the previous lists: processor, memory, disk, and network.
Remember that these counters are just the normal ones for each subsystem, but you have many more options that can be used for advanced monitoring scenarios.
Now, with logged monitoring in place, you can analyze, investigate, and evaluate your existing environment, finding the normal baseline and using it to track any anomaly easily. The baseline results will also help you to identify when a tuning or an upgrade is necessary.
3.138.175.180