Monitor and manage your deployment 编辑

Citrix Hypervisor provides detailed monitoring of performance metrics. These metrics include CPU, memory, disk, network, C-state/P-state information, and storage. Where appropriate, these metrics are available on a per host and a per VM basis. These metrics are available directly, or can be accessed and viewed graphically in Citrix Hypervisor Center or other third-party applications.

Citrix Hypervisor also provides system and performance alerts. Alerts are notifications that occur in response to selected system events. These notifications also occur when one of the following values goes over a specified threshold on a managed host, VM, or storage repository: CPU usage, network usage, memory usage, control domain memory usage, storage throughput, or VM disk usage. You can configure the alerts by using the xe CLI or by using Citrix Hypervisor Center. To create notifications based on any of the available Host or VM performance metrics see Performance alerts.

Monitor Citrix Hypervisor performance

Customers can monitor the performance of their Citrix Hypervisor servers and Virtual Machines (VMs) using the metrics exposed through Round Robin Databases (RRDs). These metrics can be queried over HTTP or through the RRD2CSV tool. In addition, Citrix Hypervisor Center uses this data to produce system performance graphs. For more information, see Analyze and visualize metrics.

The following tables list all of the available Host and VM metrics.

Notes:

  • Latency over a period is defined as the average latency of operations during that period.
  • The availability and utility of certain metrics are SR and CPU dependent.
  • Performance metrics are not available for GFS2 SRs and disks on those SRs.

Available host metrics

Metric NameDescriptionConditionCitrix Hypervisor Center Name
avgqu_sz_<sr-uuid-short>Average I/O queue size (requests).At least one plugged VBD in SR <sr-uuid-short> on the hostsr-uuid-short Queue Size
cpu<cpu>-C<cstate>Time CPU cpu spent in C-state cstate in milliseconds.C-state exists on CPUCPU cpu C-state cstate
cpu<cpu>-P<pstate>Time CPU cpu spent in P-state pstate in milliseconds.P-state exists on CPUCPU cpu P-state pstate
cpu<cpu>Utilization of physical CPU cpu (fraction). Enabled by default.CPU cpu existsCPU cpu
cpu_avgMean utilization of physical CPUs (fraction). Enabled by default.NoneAverage CPU
inflight_<sr-uuid-short>Number of I/O requests currently in flight. Enabled by default.At least one plugged VBD in SR sr on the hostsr Inflight Requests
io_throughput_read_<sr-uuidshort>Data read from SR (MiB/s).At least one plugged VBD in SR sr on the hostsr Read Throughput
io_throughput_write_<sr-uuidshort>Data written to the SR (MiB/s).At least one plugged VBD in SR sr on the hostsr Write Throughput
io_throughput_total_<sr-uuidshort>All SR I/O (MiB/s).At least one plugged VBD in SR sr on the hostsr Total Throughput
iops_read_<sr-uuid-short>Read requests per second.At least one plugged VBD in SR sr on the hostsr Read IOPS
iops_write_<sr-uuid-short>Write requests per second.At least one plugged VBD in SR sr on the hostsr Write IOPS
iops_total_<sr-uuid-short>I/O requests per second.At least one plugged VBD in SR sr on the hostsr Total IOPS
iowait_<sr-uuid-short>Percentage of the time waiting for I/O.At least one plugged VBD in SR sr on the hostsr IO Wait
latency_<sr-uuid-short>Average I/O latency (milliseconds).At least one plugged VBD in SR sr on the hostsr Latency
loadavgDomain0 load average. Enabled by defaultNoneControl Domain Load
memory_free_kibTotal amount of free memory (KiB). Enabled by default.NoneFree Memory
memory_reclaimedHost memory reclaimed by squeeze (B).NoneReclaimed Memory
memory_reclaimed_maxHost memory available to reclaim with squeeze (B).NonePotential Reclaimed Memory
memory_total_kibTotal amount of memory (KiB) in the host. Enabled by default.NoneTotal Memory
network/latencyInterval in seconds between the last two heartbeats transmitted from the local host to all Online hosts. Disabled by default.HA EnabledNetwork Latency
statefile/<t>/latencyTurn-around time in seconds of the latest State-File access from the local host. Disabled by default.HA EnabledHA State File Latency
pif_<pif>_rxBytes per second received on physical interface pif. Enabled by default.PIF existsXenCenter-pifname Receive (see note)
pif_<pif>_txBytes per second sent on physical interface pif. Enabled by default.PIF existsXenCenter-pifname Send (see note)
pif_<pif>_rx_errorsReceive errors per second on physical interface pif. Disabled by default.PIF existsXenCenter-pifname Receive Errors (see note)
pif_<pif>_tx_errorsTransmit errors per second on physical interface pif . Disabled by defaultPIF existsXenCenter-pifname Send Errors (see note)
pif_aggr_rxBytes per second received on all physical interfaces. Enabled by default.NoneTotal NIC Receive
pif_aggr_txBytes per second sent on all physical interfaces. Enabled by default.NoneTotal NIC Send
pvsaccelerator_evictedBytes per second evicted from the cachePVSAccelerator EnabledPVS-Accelerator eviction rate
pvsaccelerator_read_hitsReads per second served from the cachePVSAccelerator EnabledPVS-Accelerator hit rate
pvsaccelerator_read_missesReads per second that cannot be served from the cachePVSAccelerator EnabledPVS-Accelerator miss rate
pvsaccelerator_traffic_client_sentBytes per second sent by cached PVS clientsPVSAccelerator EnabledPVS-Accelerator observed network traffic from clients
pvsaccelerator_traffic_server_sentBytes per second sent by cached PVS serversPVSAccelerator EnabledPVS-Accelerator observed network traffic from servers
pvsaccelerator_read_totalReads per second observed by the cachePVSAccelerator EnabledPVS-Accelerator observed read rate
pvsaccelerator_traffic_proxy_savedBytes per second sent by PVSAccelerator instead of the PVS serverPVSAccelerator EnabledPVS-Accelerator saved network traffic
pvsaccelerator_space_utilizationPercentage of space used by PVSAccelerator on this host, compared to the total size of the cache storagePVSAccelerator EnabledPVS-Accelerator space utilization
sr_<sr>_cache_sizeSize in bytes of the IntelliCache SR. Enabled by default.IntelliCache EnabledIntelliCache Cache Size
sr_<sr>_cache_hitsCache hits per second. Enabled by default.IntelliCache EnabledIntelliCache Cache Hits
sr_<sr>_cache_missesCache misses per second. Enabled by default.IntelliCache EnabledIntelliCache Cache Misses
xapi_allocation_kibMemory (KiB) allocation done by the XAPI daemon. Enabled by default.NoneAgent Memory Allocation
xapi_free_memory_kibFree memory (KiB) available to the XAPI daemon. Enabled by default.NoneAgent Memory Free
xapi_live_memory_kibLive memory (KiB) used by XAPI daemon. Enabled by default.NoneAgent Memory Live
xapi_memory_usage_kibTotal memory (KiB) allocated used by XAPI daemon. Enabled by default.NoneAgent Memory Usage

Available VM metrics

Metric NameDescriptionConditionCitrix Hypervisor Center Name
cpu<cpu>Utilization of vCPU cpu (fraction). Enabled by defaultvCPU cpu existsCPU
memoryMemory currently allocated to VM (Bytes).Enabled by defaultNoneTotal Memory
memory_targetTarget of VM balloon driver (Bytes). Enabled by defaultNoneMemory target
memory_internal_freeMemory used as reported by the guest agent (KiB). Enabled by defaultNoneFree Memory
runstate_fullrunFraction of time that all vCPUs are running.NonevCPUs full run
runstate_full_contentionFraction of time that all vCPUs are runnable (that is, waiting for CPU)NonevCPUs full contention
runstate_concurrency_hazardFraction of time that some vCPUs are running and some are runnableNonevCPUs concurrency hazard
runstate_blockedFraction of time that all vCPUs are blocked or offlineNonevCPUs idle
runstate_partial_runFraction of time that some vCPUs are running, and some are blockedNonevCPUs partial run
runstate_partial_contentionFraction of time that some vCPUs are runnable and some are blockedNonevCPUs partial contention
vbd_<vbd>_writeWrites to device vbd in bytes per second. Enabled by defaultVBD vbd existsDisk vbd Write
vbd_<vbd>_readReads from device vbd in bytes per second. Enabled by default.VBD vbd existsDisk vbd Read
vbd_<vbd>_write_latencyWrites to device vbd in microseconds.VBD vbd existsDisk vbd Write Latency
vbd_<vbd>_read_latencyReads from device vbd in microseconds.VBD vbd existsDisk vbd Read Latency
vbd <vbd>_iops_readRead requests per second.At least one plugged VBD for non-ISO VDI on the hostDisk vbd Read IOPs
vbd <vbd>_iops_writeWrite requests per second.At least one plugged VBD for non-ISO VDI on the hostDisk vbd Write IOPS
vbd <vbd>_iops_totalI/O requests per second.At least one plugged VBD for non-ISO VDI on the hostDisk vbd Total IOPS
vbd <vbd>_iowaitPercentage of time waiting for I/0.At least one plugged VBD for non-ISO VDI on the hostDisk vbd IO Wait
vbd <vbd>_inflightNumber of I/O requests currently in flight.At least one plugged VBD for non-ISO VDI on the hostDisk vbd Inflight Requests
vbd <vbd>_avgqu_szAverage I/O queue size.At least one plugged VBD for non-ISO VDI on the hostDisk vbd Queue Size
vif_<vif>_rxBytes per second received on virtual interface number vif. Enabled by default.VIF vif existsvif Receive
vif_<vif>_txBytes per second transmitted on virtual interface vif. Enabled by default.VIF vif existsvif Send
vif_<vif>_rx_errorsReceive errors per second on virtual interface vif. Enabled by default.VIF vif existsvif Receive Errors
vif_<vif>_tx_errorsTransmit errors per second on virtual interface vif Enabled by default.VIF vif existsvif Send Errors

Note:

The value of <XenCenter-pif-name> can be any of the following:

  
NIC <pif>If <pif> contains pif_eth#, where ## is 0–9
<pif>If <pif> contains pif_eth#.## or pif_xenbr## or pif_bond##
<Internal> Network <pif>If <pif> contains pif_xapi##, (note that <Internal> appears as is)
TAP <tap>If <pif> contains pif_tap##
xapi LoopbackIf <pif> contains pif_lo

Analyze and visualize metrics

The Performance tab in Citrix Hypervisor Center provides real time monitoring of performance statistics across resource pools in addition to graphical trending of virtual and physical machine performance. Graphs showing CPU, memory, network, and disk I/O are included on the Performance tab by default. You can add more metrics, change the appearance of the existing graphs or create extra ones. For more information, see Configuring metrics in the following section.

  • You can view up to 12 months of performance data and zoom in to take a closer look at activity spikes.

  • Citrix Hypervisor Center can generate performance alerts when CPU, memory, network I/O, storage I/O, or disk I/O usage exceed a specified threshold on a server, VM, or SR. For more information, see Alerts in the following section.

Note:

Install the Citrix VM Tools to see full VM performance data.

Configure performance graphs

To add a graph:

  1. On the Performance tab, click Actions and then New Graph. The New Graph dialog box is displayed.

  2. In the Name field, enter a name for the graph.

  3. From the list of Datasources, select the check boxes for the datasources you want to include in the graph.

  4. Click Save.

To edit an existing graph:

  1. Navigate to the Performance tab, and select the graph that you would like to modify.

  2. Right-click on the graph and select Actions, or click the Actions button. Then select Edit Graph.

  3. On the graph details window, make the necessary changes, and click OK.

Configure the graph type

Data on the performance graphs can be displayed as lines or as areas. To change the graph type:

  1. On the Tools menu, click Options and select Graphs.

  2. To view performance data as a line graph, click the Line graph option.

  3. To view performance data as an area graph, click the Area graph option.

  4. Click OK to save your changes.

Comprehensive details for configuring and viewing Citrix Hypervisor Center performance graphs can be found in the Citrix Hypervisor Center documentation in the section Monitoring System Performance.

Configure metrics

Note:

C-states and P-states are power management features of some processors. The range of states available depends on the physical capabilities of the host, as well power management configuration.

Both host and VM commands return the following:

  • A full description of the data source

  • The units applied to the metric

  • The range of possible values that may be used

For example:

    name_label: cpu0-C1
    name_description: Proportion of time CPU 0 spent in C-state 1
    enabled: true
    standard: true
    min: 0.000
    max: 1.000
    units: Percent
<!--NeedCopy-->

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据

词条统计

浏览:94 次

字数:28770

最后编辑:7 年前

编辑次数:0 次

    我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
    原文