<%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


  • This sensor has a high performance impact. Use it with care. We recommend that you use no more than 200 sensors of this sensor type on each probe.
  • The parent device must be a Citrix XenServer version 5.0 or later.
  • The parent device must represent one host server of your XenServer pool.
  • This sensor requires Microsoft .NET 4.7.2 or later on the probe system.
  • This sensor requires credentials for VMware/XenServer in the settings of the parent device.
  • This sensor does not fully support Transport Layer Security (TLS) 1.2 connections and cannot be added to XenServers with the security protocol setting "TLS 1.2 only".
  • This sensor only supports the IPv4 protocol.

Detailed Requirements



.NET 4.7.2 or later

This sensor requires .NET 4.7.2 or later to be installed on the probe system (on every cluster node, if on a cluster probe).

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?

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.

Add Sensor

The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the settings that are required to create the sensor. You can change nearly all settings on the sensor's Settings tab after creation.

i_round_blueThe settings that you select in the Add Sensor dialog are valid for all sensors that you create when you finish the dialog.

Host Settings




Select the XenServer hosts that you want to monitor, including hosts that do not run. PRTG creates one sensor for each host that you select.

i_round_blueEnable check boxes in front of the respective lines to select the items. Use the check box in the table header to select all items or to cancel the selection. In large tables, use the search function in the upper-right corner.

Basic Sensor Settings

Click the Settings tab of a sensor to change its settings.

Basic Sensor Settings

Basic Sensor Settings



Sensor Name

Enter a name to identify the sensor.

Parent Tags

Shows tags that the sensor inherits from its parent device, parent group, and parent probe.

i_round_blueThis setting is for your information only. You cannot change it.


Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.

i_round_blueIt is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).

i_round_blueFor performance reasons, it can take some minutes until you can filter for new tags that you added.

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

  • xenhostsensor


Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority (i_priority_1) to the highest priority (i_priority_5).

i_round_blueUsually, a sensor connects to the IP Address/DNS Name of the parent device. See the device settings for details. For some sensors, you can explicitly define the monitoring target in the sensor settings.

Host Settings

Host Settings

Host Settings




Shows 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.


Shows the name of the host that this sensor monitors.

i_round_bluePRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.

Debug Options

Debug Options

Debug Options



Result Handling

Define what PRTG does with the sensor result:

  • Discard result: 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, the last value of the primary channel is always displayed 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 different channels are shown for this sensor:

  • 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 enable Stack channels on top of each other as Graph Type. Select a unit from the list. All channels with this unit are stacked 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.

Scanning Interval

Scanning Interval

Scanning Interval

i_square_cyanFor more information, see section Root Group Settings, section Scanning Interval.

Schedules, Dependencies, and Maintenance Window

i_round_blueYou cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.

Schedules, Dependencies, and Maintenance Window

Schedules, Dependencies, and Maintenance Window

i_square_cyanFor more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.

Access Rights

Access Rights

Access Rights

i_square_cyanFor more information, see section Root Group Settings, section Access Rights.

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 in percent

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 in percent.

Load Average

The load average amount

VMs Running

The number of running virtual machines (VM)

Total Memory Free

The total memory available in bytes

Total Memory Used

The total memory used in bytes


i_square_blueKnowledge Base

Which .NET version does PRTG require?

What security features does PRTG include?

Does PRTG impair my Citrix environment?