<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Citrix XenServer Host Sensor

The Citrix XenServer Host sensor monitors a Xen host server via HTTP.

Citrix XenServer Host Sensor

Citrix XenServer Host Sensor

i_square_cyanFor a detailed list and descriptions of the channels that this sensor can show, see section Channel List.

Sensor in Other Languages

  • Dutch: Citrix XenServer Host
  • French: Citrix XenServer serveur hôte
  • German: Citrix XenServer Host
  • Japanese: Citrix XenServer ホスト
  • Portuguese: Host Citrix XenServer
  • Russian: Узел Citrix XenServer
  • Simplified Chinese: Citrix XenServer 主机
  • Spanish: Host Citrix XenServer


Consider the following remarks and requirements for this sensor:



Performance impact

  • This sensor has a high performance impact. We recommend that you use no more than 200 of this sensor on each probe.

.NET 4.7.2 or later

  • This sensor requires .NET 4.7.2 or later from Microsoft on the probe system. In a cluster, install it on every cluster node.

i_round_redIf the framework is missing, you cannot create this sensor.

i_square_cyanFor more information, see the Knowledge Base: Which .NET version does PRTG require?

Parent device

  • This sensor requires that the parent device is a Citrix XenServer as of version 5.0.
  • This sensor requires that the parent device represents one host server of your XenServer pool.


  • This sensor requires credentials for VMware/XenServer.

TLS 1.2

  • This sensor does not fully support Transport Layer Security (TLS) 1.2 connections. You cannot add it to XenServers with the security protocol setting "TLS 1.2 only".


  • This sensor only supports IPv4.

Add Sensor dialog

  • PRTG also includes hosts that do not run in the Add Sensor dialog.

Monitoring a XenServer Pool

In a XenServer pool, there is one "pool master" that manages the pool. Incoming queries on any host are automatically forwarded to the pool master. If you want to monitor your VMs or host servers, create respective sensors on a device that represents one host server of your pool. Internal processes make sure that monitoring takes place and continues independently from the physical host.

i_round_blueIn the device tree, the sensors for VMs always remain on the host you originally created them on, also if they are currently running on a different host.

Basic Sensor Settings

Basic Sensor Settings

Basic Sensor Settings

The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:

  • xenhostsensor

i_square_cyanFor more information about basic sensor settings, see section Sensor Settings.

Host Settings

Host Settings

Host Settings




The universally unique identifier (UUID) of the host that this sensor monitors.

i_round_redPRTG shows this value for reference purposes only. We strongly recommend that you only change it if the Paessler support team explicitly asks you to do so. Wrong usage can result in incorrect monitoring data.


The name of the host that this sensor monitors.

Debug Options

Debug Options

Debug Options



Result Handling

Define what PRTG does with the sensor result:

  • Discard result (default): Do not store the sensor result.
  • Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file names are Result of Sensor [ID].txt and Result of Sensor [ID].Data.txt. This setting is for debugging purposes. PRTG overwrites these files with each scanning interval.

i_podThis option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.

i_round_blueIn a cluster, PRTG stores the result in the PRTG data directory of the master node.

Sensor Display

Sensor Display

Sensor Display



Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, PRTG displays the last value of the primary channel below the sensor's name. The available options depend on what channels are available for this sensor.

i_round_blueYou can set a different primary channel later by clicking b_channel_primary below a channel gauge on the sensor's Overview tab.

Graph Type

Define how this sensor shows different channels:

  • Show channels independently (default): Show a graph for each channel.
  • Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
    i_round_redYou cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).

Stack Unit

This setting is only visible if you select Stack channels on top of each other above.

Select a unit from the list. PRTG stacks all channels with this unit on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so.

Inherited Settings

By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click b_inherited_enabled under the corresponding setting name to disable the inheritance and to display its options.

i_square_cyanFor more information, see section Inheritance of Settings.

Channel List

i_round_blueWhich channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.



CPU [Value] Usage

The CPU usage

i_round_blueThis channel is the primary channel by default.


In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status

Load Average

The load average amount

VMs Running

The number of running VMs

Total Memory Free

The total memory available

Total Memory Used

The total memory used


i_square_blueKNOWLEDGE BASE

Which .NET version does PRTG require?

What security features does PRTG include?

Does PRTG impair my Citrix environment?