Workload Balancing displays the average for each hour for the time period you set. The data point is based on a utilization average for that hour for all days in the time period. For example, in a report for May1, 2009 to May 15, 2009, the Average CPU Usage data point represents the resource utilization of all fifteen days at 12:00 hours combined together as an average. That is, if CPU utilization was 82% at 12PM on May 1st, 88% at 12PM on May 2nd, and 75% on all other days, the average displayed for 12PM is 76.3%.
Note:
Workload Balancing smooths spikes and peaks so data does not appear artificially high.
Pool Optimization Performance History
The optimization performance report displays optimization events (that is, when you optimized a resource pool) against that pool's average resource usage. Specifically, it displays resource usage for CPU, memory, network reads, and network writes.
The dotted line represents the average usage across the pool over the period of days you select. A blue bar indicates the day on which you optimized the pool.
This report can help you determine if Workload Balancing is working successfully in your environment. You can use this report to see what led up to optimization events (that is, the resource usage before Workload Balancing recommended optimizing).
This report displays average resource usage for the day; it does not display the peak utilization, such as when the system is stressed. You can also use this report to see how a resource pool is performing if Workload Balancing is not making optimization recommendations.
In general, resource usage should decline or be steady after an optimization event. If you do not see improved resource usage after optimization, consider readjusting threshold values. Also, consider whether or not the resource pool has too many virtual machines and whether or not new virtual machines were added or removed during the time frame you specified.
Pool Audit Log History
This report displays the contents of the XenServer Audit Log, a XenServer feature designed to log attempts to perform unauthorized actions and select authorized actions, including import/export, host and pool back ups, and guest and host console access. For information about the Audit Log feature, see the audit log documentation in the XenCenter online help or the[ XenServer Administrator's Guide].
To run the audit log report, the Audit Logging feature must be enabled, which it is by default.
This report displays the following:
•Time. The time XenServer recorded the user's action.
•Host Name. The name of the physical server on which the user performed the action (where the action occurred).
•User Name. The name of the person who created the session in which the action was performed. In some cases, this may be the User ID.
•Access. Whether or not the user had permission to perform the action.
•Call Type. The Call Type indicates whether the user connected to the session over the Internet or locally. For example, if the user connected to XenCenter over the Internet.
•Event Object. The object that was the subject of the action (for example, a VM).
•Object Name. The name of the object (for example, the name of the VM).
119
