PRTG Manual: Citrix XenServer Host Sensor
The Citrix XenServer Host sensor monitors a Xen host server via HTTP.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- 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. We recommend that you use no more than 200 of this sensor on each probe.
- This sensor requires .NET 4.7.2 or later from Microsoft on the probe system.
- 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 in the settings of the parent device.
- 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.
- PRTG also includes hosts that do not run in the Add Sensor dialog.
Requirement |
Description |
---|---|
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).
|
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.
In 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.
Setting |
Description |
---|---|
Sensor Name |
Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.
|
Parent Tags |
The tags that the sensor inherits from its parent device, parent group, and parent probe.
|
Tags |
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.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
|
Priority |
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 ( |
Setting |
Description |
---|---|
UUID |
The universally unique identifier (UUID) of the host that this sensor monitors.
|
Name |
The name of the host that this sensor monitors. |
Setting |
Description |
---|---|
Result Handling |
Define what PRTG does with the sensor result:
|
Setting |
Description |
---|---|
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.
|
Graph Type |
Define how different channels are shown for this sensor:
|
Stack Unit |
This setting is only visible if you select Stack channels on top of each other above. 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. |
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 under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Inheritance of Settings.
For more information, see section Root Group Settings, section Scanning Interval.
Schedules, Dependencies, and Maintenance Window
You 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.
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
For more information, see section Root Group Settings, section Access Rights.
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel |
Description |
---|---|
CPU [Value] Usage |
The CPU usage
|
Downtime |
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 |
KNOWLEDGE BASE
Which .NET version does PRTG require?
What security features does PRTG include?
Does PRTG impair my Citrix environment?