Display Name | Citrix Management Pack Library |
---|---|
Version | 1.0.8.0 |
Description | Common definitions for Citrix Management Packs. |
Display Name | Citrix Management Pack for XenApp 6.x |
---|---|
Version | 1.43.20693.0 |
Description | Provides the complete management of the Citrix XenApp environment. |
Display Name | Citrix Management Pack for XenApp 6.x Reports |
---|---|
Version | 1.43.20693.0 |
Description | Provides reports for the Citrix XenApp environment. |
Target | Display Name | Description | Enabled by default | Discovery interval |
---|---|---|---|---|
Application Data Collector | XenApp Farm Applications Discovery (1 of 2) | Discovers applications in a farm. This is the first of two discoveries. Each discovery can provide up to 800 applications. Discovered applications can be filtered based on regular expression pattern matching against the application full path ("Applications/Folder1/ApplicationA"). With it applications can be filtered based on application name or folder name. Use the following overridable parameters to limit discovery: FilterExclude - Accepts regular expression pattern representing applications to be excluded from discovery. FilterInclude - Accepts regular expression pattern representing applications to be included in discovery. * "Filter" parameter is obsolete and is ignored. When updating FilterExclude or FilterInclude parameter, copy their value to FilterExclude/FilterInclude parameter in 'XenApp Farm Applications Discovery (2 of 2)' and 'XenApp Server Discovery' discovery. Regular expression examples: Match any application belonging to certain folder (Folder1) and subfolders. ^Applications/Folder1/.*$ Match any application belonging to folders starting with certain pattern (TestFold) or folders with exact name (Folder1 or Folder2). (.*/TestFold[^/]*/[^/]*|.*/Folder1/[^/]*|.*/Folder2/[^/]*)$ Match any application whose name starts with certain pattern (ApplicationC), regardless of parent folder. .*/ApplicationC[^/]*$ Match any application whose name contains certain pattern (licationD), regardless of parent folder. .*/.*licationD[^/]*$ Match specific application(s) specified with full path. ^(Applications/Folder1/ApplicationA|Applications/Folder2/Folder3/ApplicationB)$ Match all applications with exact name, regardless of parent folder. .*/ApplicationC$ Match any application belonging either to Folder1 or Folder5 (with their subfolders) or application name starts with "ApplicationC" (in any folder). (.*/Folder1/.*|.*/Folder5/.*|.*/ApplicationC[^/]*)$ Match any application belonging to Folder1 or Folder5 (with their subfolders) where application name starts with "ApplicationC". .*/(Folder1|Folder5)(/.*/|/)ApplicationC[^/]*$ |
Yes | 3600 sec |
Application Data Collector | XenApp Farm Applications Discovery (2 of 2) | Discovers applications in a farm. This is the second of two discoveries. Each discovery can provide up to 800 applications. Discovered applications can be filtered based on regular expression pattern matching against the application full path ("Applications/Folder1/ApplicationA"). With it applications can be filtered based on application name or folder name. Use the following overridable parameters to limit discovery: FilterExclude - Accepts regular expression pattern representing applications to be excluded from discovery. FilterInclude - Accepts regular expression pattern representing applications to be included in discovery. * "Filter" parameter is obsolete and is ignored. When updating FilterExclude or FilterInclude parameter, copy their value to FilterExclude/FilterInclude parameter in 'XenApp Farm Applications Discovery (1 of 2)' and 'XenApp Server Discovery' discovery. Regular expression examples: Match any application belonging to certain folder (Folder1) and subfolders. ^Applications/Folder1/.*$ Match any application belonging to folders starting with certain pattern (TestFold) or folders with exact name (Folder1 or Folder2). (.*/TestFold[^/]*/[^/]*|.*/Folder1/[^/]*|.*/Folder2/[^/]*)$ Match any application whose name starts with certain pattern (ApplicationC), regardless of parent folder. .*/ApplicationC[^/]*$ Match any application whose name contains certain pattern (licationD), regardless of parent folder. .*/.*licationD[^/]*$ Match specific application(s) specified with full path. ^(Applications/Folder1/ApplicationA|Applications/Folder2/Folder3/ApplicationB)$ Match all applications with exact name, regardless of parent folder. .*/ApplicationC$ Match any application belonging either to Folder1 or Folder5 (with their subfolders) or application name starts with "ApplicationC" (in any folder). (.*/Folder1/.*|.*/Folder5/.*|.*/ApplicationC[^/]*)$ Match any application belonging to Folder1 or Folder5 (with their subfolders) where application name starts with "ApplicationC". .*/(Folder1|Folder5)(/.*/|/)ApplicationC[^/]*$ |
Yes | 3600 sec |
XenApp Computer Role | Citrix XenApp MP Agent Service Discovery | Discovers Citrix Management Pack Agent for XenApp 6.x used for monitoring the XenApp infrastructure. |
Yes | 3600 sec |
Windows Computer | Citrix Computer Discovery | Discovers managed nodes with Citrix software installed on it. |
Yes | 3600 sec |
Windows Computer | XenApp Computer Role Discovery | Discovers managed nodes with Citrix XenApp Server installed on it. Discovered nodes can be seen in the "XenApp 6.x Computers" view within the "Citrix Library" folder. |
Yes | 3600 sec |
XenApp | XenApp Server Services Discovery | Discovers XenApp and Terminal Server services. |
Yes | 3600 sec |
XenApp Computer Role | XenApp Server Discovery | Discovers XenApp servers, farms, and zones. Applications can be excluded from discovery based on regular expression pattern matching against the application full path ("Applications/Folder1/ApplicationA"). With it applications can be filtered based on application name or folder name. Use the following overridable parameters to limit discovery: FilterExclude - Accepts regular expression pattern representing applications to be excluded from discovery. FilterInclude - Accepts regular expression pattern representing applications to be included in discovery. * "Filter" parameter is obsolete and is ignored. When updating FilterExclude or FilterInclude parameter, copy their value to FilterExclude/FilterInclude parameter in 'XenApp Farm Applications Discovery (1 of 2)' and 'XenApp Farm Applications Discovery (2 of 2)' discovery. Regular expression examples: Match any application belonging to certain folder (Folder1) and subfolders. ^Applications/Folder1/.*$ Match any application belonging to folders starting with certain pattern (TestFold) or folders with exact name (Folder1 or Folder2). (.*/TestFold[^/]*/[^/]*|.*/Folder1/[^/]*|.*/Folder2/[^/]*)$ Match any application whose name starts with certain pattern (ApplicationC), regardless of parent folder. .*/ApplicationC[^/]*$ Match any application whose name contains certain pattern (licationD), regardless of parent folder. .*/.*licationD[^/]*$ Match specific application(s) specified with full path. ^(Applications/Folder1/ApplicationA|Applications/Folder2/Folder3/ApplicationB)$ Match all applications with exact name, regardless of parent folder. .*/ApplicationC$ Match any application belonging either to Folder1 or Folder5 (with their subfolders) or application name starts with "ApplicationC" (in any folder). (.*/Folder1/.*|.*/Folder5/.*|.*/ApplicationC[^/]*)$ Match any application belonging to Folder1 or Folder5 (with their subfolders) where application name starts with "ApplicationC". .*/(Folder1|Folder5)(/.*/|/)ApplicationC[^/]*$ |
Yes | 3600 sec |
XenApp Farms | Populate XenApp Farms | Makes containment relationships between a farm and the "XenApp Farms" object. |
Yes | --- |
Application | Published Application to XenApp Availability Relationship Discovery | Makes containment relationships between the "XenApp Availability" and the "Application" object. |
Yes | --- |
Citrix Management | Populate Citrix Library | Makes containment relationships between the "XenApp Farms" and the "Citrix Management" object. |
Yes | --- |
Display Name | XenApp Application Accessibility | |
---|---|---|
Description | Monitors whether the application is enabled. | |
Knowledge Article |
SummaryAlerts if an application is currently in disabled state. Disabled applications are not available to end-users. | |
Target | Application | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Enabled | Healthy |
Disabled | Warning |
Display Name | Citrix XenApp MP Agent Operational Status | |
---|---|---|
Description | Monitors if Citrix XenApp MP Agent is operational. | |
Knowledge Article |
SummaryThis monitor checks if Citrix XenApp MP Agent is operational. ConfigurationCitrix XenApp MP Agent may not be operational for many reasons, including:
To get detailed information why agent is not operational run "Check Requirements and Configuration for Citrix MPXA Agent" task. | |
Alert Name | Citrix XenApp MP Agent Operational Status | |
Alert Message | Citrix XenApp MP Agent is not operational. To get detailed information why agent is not operational run "Check Requirements and Configuration for Citrix MPXA Agent" task. | |
Target | Citrix XenApp MP Agent Service | |
Enabled by default | Yes |
Monitor State | Health State |
---|---|
OK | Healthy |
Error | Critical |
Parameter | Default Value |
---|---|
IntervalSeconds | 1800 |
Display Name | Citrix XenApp MP Agent Service State | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | Monitors the Citrix XenApp MP Agent mandatory service. | |||||||||
Knowledge Article |
SummaryThe Citrix XenApp MP Agent mandatory service is not running. CausesA service can stop for many reasons, including:
ResolutionsStart the service from the “Actions” pane. AdditionalThe topology and the health state of your Citrix XenApp environment managed by this agent will not be properly updated if the service is not running. | |||||||||
Alert Name | Citrix XenApp MP Agent Service Stopped | |||||||||
Alert Message | The "{0}" service on computer {1} has stopped running. | |||||||||
Target | Citrix XenApp MP Agent Service | |||||||||
Enabled by default | Yes |
Monitor State | Health State |
---|---|
Service is running | Healthy |
Service is not running | Critical |
Parameter | Default Value |
---|---|
CheckStartupType | true |
Display Name | XenApp Service State Monitor | |
---|---|---|
Description | Monitors the Citrix XenApp services state. | |
Knowledge Article |
SummaryThe Windows service is not running. CausesA service can stop for many reasons, including:
ResolutionsStart the service from the “Actions” pane. | |
Alert Name | Windows Service Stopped | |
Alert Message | The "{0}" service on computer {1} has stopped running. | |
Target | XAMP Windows Service | |
Enabled by default | Yes |
Monitor State | Health State |
---|---|
ServiceRunning | Healthy |
ServiceNotRunning | Critical |
Parameter | Default Value |
---|---|
CheckStartupType | true |
Display Name | Active XenApp Sessions | |
---|---|---|
Description | Monitors the number of active sessions on a server. | |
Knowledge Article |
SummaryAlerts if the number of sessions in an active state is high. Sessions in an active state are end-user sessions that are currently in progress. This helps to identify a potentially overloaded server, or if load balancing is not working correctly. See also the XenApp Session Summary Performance View for details. | |
Alert Name | Active XenApp Sessions | |
Alert Message | The number of active sessions on {0} has exceeded the threshold value. Active sessions: {1} | |
Target | XenApp | |
Enabled by default | No |
Monitor State | Health State |
---|---|
GreaterThanEqualCriticalThreshold | Critical |
GreaterThanEqualWarningThreshold | Warning |
LessThanWarningThreshold | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
ThresholdCriticalValue | 1000 |
ThresholdWarningValue | 500 |
Display Name | All XenApp Sessions | |
---|---|---|
Description | Monitors the number of all sessions on a server. | |
Knowledge Article |
SummaryAlerts if the total number of sessions in all possible states is high. See also the XenApp Session Summary Performance View for details. | |
Alert Name | All XenApp Sessions | |
Alert Message | The number of all sessions on {0} has exceeded the threshold value. All sessions: {1} | |
Target | XenApp | |
Enabled by default | No |
Monitor State | Health State |
---|---|
GreaterThanEqualCriticalThreshold | Critical |
GreaterThanEqualWarningThreshold | Warning |
LessThanWarningThreshold | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
ThresholdCriticalValue | 1000 |
ThresholdWarningValue | 500 |
Display Name | Disconnected XenApp Sessions | |
---|---|---|
Description | Monitors the number of disconnected sessions on a server. | |
Knowledge Article |
SummaryAlerts if the number of sessions in a disconnected state is high. Large number of disconnected sessions may be normal, but can also indicate a sudden drop of end-user connectivity. See also the XenApp Session Summary Performance View for details. | |
Alert Name | Disconnected XenApp Sessions | |
Alert Message | The number of disconnected sessions on {0} has exceeded the threshold value. Disconnected sessions: {1} | |
Target | XenApp | |
Enabled by default | Yes |
Monitor State | Health State |
---|---|
GreaterThanEqualCriticalThreshold | Critical |
GreaterThanEqualWarningThreshold | Warning |
LessThanWarningThreshold | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
ThresholdCriticalValue | 100 |
ThresholdWarningValue | 50 |
Display Name | Down XenApp Sessions | |
---|---|---|
Description | Monitors the number of down sessions on a server. | |
Knowledge Article |
SummaryAlerts if the number of sessions in a down state is high. Sessions in a down state typically indicate sessions that did not log off correctly / hung during logoff. Sometimes it is even difficult to “kill” them, so the only thing that helps is a reboot. See also the XenApp Session Summary Performance View for details. | |
Alert Name | Down XenApp Sessions | |
Alert Message | The number of down sessions on {0} has exceeded the threshold value. Down sessions: {1} | |
Target | XenApp | |
Enabled by default | Yes |
Monitor State | Health State |
---|---|
GreaterThanEqualCriticalThreshold | Critical |
GreaterThanEqualWarningThreshold | Warning |
LessThanWarningThreshold | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
ThresholdCriticalValue | 15 |
ThresholdWarningValue | 8 |
Display Name | Total File Count of All User Profiles | |
---|---|---|
Description | Monitors the total file count of all user profiles. | |
Knowledge Article |
SummaryAlerts if there is a large number of files across all user profiles. | |
Alert Name | Total File Count of All User Profiles | |
Alert Message | XenApp total file count of all user profiles on {0} has exceeded the threshold value. Total file count: {1} | |
Target | XenApp | |
Enabled by default | No |
Monitor State | Health State |
---|---|
GreaterThanEqualThreshold | Warning |
LessThanThreshold | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
ThresholdValue | 500000 |
Display Name | Total File Size of All User Profiles | |
---|---|---|
Description | Monitors the total file size of all user profiles. | |
Knowledge Article |
SummaryAlerts if there is a large volume of files across all user profiles. | |
Alert Name | Total File Size of All User Profiles | |
Alert Message | XenApp total file size of all user profiles on {0} has exceeded the threshold value. Total file size: {1} MB | |
Target | XenApp | |
Enabled by default | No |
Monitor State | Health State |
---|---|
GreaterThanEqualThreshold | Warning |
LessThanThreshold | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
ThresholdValue | 10000 |
Display Name | XenApp Installation Drive Free Space | |
---|---|---|
Description | Monitors free space (in MB) on XenApp installation drive. | |
Knowledge Article |
SummaryMonitors free space (in MB) on XenApp installation drive. | |
Alert Name | XenApp Installation Drive Free Space | |
Alert Message | Free space on XenApp installation drive on {0} is below the threshold value. Drive: {1} Drive type: {2} Capacity: {3} MB Free space: {4} MB | |
Target | XenApp | |
Enabled by default | Yes |
Monitor State | Health State |
---|---|
OK | Healthy |
Warning | Warning |
Critical | Critical |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
WarningThreshold | 500 |
CriticalThreshold | 100 |
Display Name | XenApp Installation Drive Free Space Percentage | |
---|---|---|
Description | Monitors the percentage of free space on XenApp installation drive. | |
Knowledge Article |
SummaryMonitors the percentage of free space on XenApp installation drive. | |
Alert Name | XenApp Installation Drive Free Space Percentage | |
Alert Message | Percentage of free space on XenApp installation drive on {0} is below the threshold value. Drive: {1} Drive type: {2} Capacity: {3} MB Free space: {4} % | |
Target | XenApp | |
Enabled by default | No |
Monitor State | Health State |
---|---|
OK | Healthy |
Warning | Warning |
Critical | Critical |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
WarningThreshold | 10 |
CriticalThreshold | 5 |
Display Name | XenApp Logons | |
---|---|---|
Description | Monitors whether the logons to the XenApp server are enabled. | |
Knowledge Article |
SummaryAlerts if logons to the server are disabled. During the maintenance hours, logons to XenApp servers are typically disabled to prevent users to connect to them. This alert will remind admins that logons to a server need to be re-enabled. | |
Alert Name | XenApp Logons | |
Alert Message | XenApp logons on {0} are disabled. | |
Target | XenApp | |
Enabled by default | No |
Monitor State | Health State |
---|---|
LogonsEnabled | Healthy |
LogonsDisabled | Warning |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Server Application Enumerations per Second | |||||||
---|---|---|---|---|---|---|---|---|
Description | This monitor checks the number of non-XML-based enumerations (requests for application lists) per second. Threshold must be configured to suit the environment configuration/setup before enabling this monitor. | |||||||
Knowledge Article |
SummaryThis monitor checks the number of non-XML-based enumerations (requests for application lists) per second over multiple consecutive samples. By default monitor is disabled because baseline needs to be established in your environment before appropriate threshold can be defined that would indicate load that could lead to decreased XML Broker performance. ConfigurationOverridable parameters:
AdditionalTo see monitor performance values, open XenApp Server Performance view. | |||||||
Alert Name | Application Enumerations per Second Too High | |||||||
Alert Message | The number of application enumerations per second on {0} has exceeded the threshold value. Current application enumerations per second: {1} Consecutive samples: {2} | |||||||
Target | XenApp | |||||||
Enabled by default | No |
Monitor State | Health State |
---|---|
OverThreshold | Warning |
UnderThreshold | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Threshold | 99999 |
NumberOfSamples | 3 |
Display Name | XenApp Server Application Resolution Time | |||||||
---|---|---|---|---|---|---|---|---|
Description | This monitor checks the time in milliseconds that a resolution took to complete. Threshold must be configured to suit the environment configuration/setup before enabling this monitor. | |||||||
Knowledge Article |
SummaryThis monitor checks the time (in milliseconds) required to resolve the Least-Loaded Server during an application launch. Alert is triggered when threshold is exceeded for configured number of consecutive samples. By default monitor is disabled because baseline would need to be established in your environment to account for increases during peak logon times before accurate thresholds can be defined. ConfigurationOverridable parameters:
AdditionalTo see monitor performance values, open XenApp Server Performance view. | |||||||
Alert Name | Application Resolution Time Too High | |||||||
Alert Message | The application resolution time on {0} has exceeded the threshold value. Current application resolution time: {1} ms Consecutive samples: {2} | |||||||
Target | XenApp | |||||||
Enabled by default | No |
Monitor State | Health State |
---|---|
OverThreshold | Warning |
UnderThreshold | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Threshold | 99999 |
NumberOfSamples | 3 |
Display Name | XenApp Server Filtered Application Enumerations per Second | |||||||
---|---|---|---|---|---|---|---|---|
Description | This monitor checks the number of XML-based enumerations (requests for application lists) per second. Threshold must be configured to suit the environment configuration/setup before enabling this monitor. | |||||||
Knowledge Article |
SummaryThis monitor checks number of XML-based enumerations per second handled by XML Broker over multiple consecutive samples. It indicates number of Web Interface/StoreFront application enumerations (and logons) per second handled by specific XML broker. By default monitor is disabled because baseline needs to be established in your environment before appropriate threshold can be defined that would indicate load that could lead to decreased XML Broker performance. ConfigurationOverridable parameters:
AdditionalTo see monitor performance values, open XenApp Server Performance view. | |||||||
Alert Name | Filtered Application Enumerations per Second Too High | |||||||
Alert Message | The number of filtered application enumerations per second on {0} has exceeded the threshold value. Current filtered application enumerations per second: {1} Consecutive samples: {2} | |||||||
Target | XenApp | |||||||
Enabled by default | No |
Monitor State | Health State |
---|---|
OverThreshold | Warning |
UnderThreshold | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Threshold | 99999 |
NumberOfSamples | 3 |
Display Name | XenApp Server Load | |
---|---|---|
Description | Monitors XenApp server load as defined by Citrix load evaluator. | |
Knowledge Article |
SummaryAlerts if server load is high. Server load is a value reported by the Citrix load evaluator that has been assigned to the server. Monitor by default ignores planned full load caused by scheduled load evaluator rules (“Citrix Maintenance Mode”). A server load of 200% (load evaluator value = 20000) indicates that a license cannot be obtained from license server. ConfigurationOverridable parameters:
| |
Alert Name | XenApp Server Load | |
Alert Message | XenApp server load on {0} has exceeded the threshold value. Server load: {1}% | |
Target | XenApp | |
Enabled by default | No |
Monitor State | Health State |
---|---|
GreaterThanEqualCriticalThreshold | Critical |
GreaterThanEqualWarningThreshold | Warning |
LessThanWarningThreshold | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
IgnoreScheduledFullLoad | true |
WarningThreshold | 70 |
CriticalThreshold | 95 |
Display Name | XenApp Server Load (Consecutive Samples) | |
---|---|---|
Description | Monitors XenApp server load as defined by Citrix load evaluator. | |
Knowledge Article |
SummaryAlerts if server load is high. Server load is a value reported by the Citrix load evaluator that has been assigned to the server. Monitor by default ignores planned full load caused by scheduled load evaluator rules (“Citrix Maintenance Mode”). A server load of 200% (load evaluator value = 20000) indicates that a license cannot be obtained from license server. ConfigurationOverridable parameters:
| |
Alert Name | XenApp Server Load (Consecutive Samples) | |
Alert Message | XenApp server load on {0} has exceeded the threshold value. Current server load: {1}% | |
Target | XenApp | |
Enabled by default | Yes |
Monitor State | Health State |
---|---|
BelowThreshold | Healthy |
AboveThreshold | Critical |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
IgnoreScheduledFullLoad | true |
Threshold | 95 |
NumberOfSamples | 3 |
Display Name | XenApp Server Number of Busy XML Threads | |||||||
---|---|---|---|---|---|---|---|---|
Description | This monitor checks the number of XML threads currently being processed. There are 16 worker threads in the Citrix XML Service. A count of 16 or more shows that XML requests are not being processed in a timely manner. | |||||||
Knowledge Article |
SummaryThis monitor checks the number of XML threads currently being processed over multiple consecutive samples. There are 16 worker threads in the Citrix XML Service. A count of 16 shows that XML requests are not being processed in a timely manner, which impacts Web Interface/Store Front requests (logons, list and launch applications) being slow or rejected. Having consistently 10 or more busy XML threads already indicate that XML broker might not be capable of servicing all request in timely manner. By default alert is generated if there are 10 or more busy XML treads on two consecutive samples (5 minutes interval). ConfigurationOverridable parameters:
CausesThe most common reason for the XML service to become unresponsive is because it is busy waiting for a response from the IMA service. Usually, adding CPU power helps reducing IMA service response times and consequently number of busy XML threads. AdditionalTo see monitor performance values, open XenApp Server Performance view. | |||||||
Alert Name | Number of Busy XML Threads Too High | |||||||
Alert Message | The number of busy XML threads on {0} has exceeded the threshold value. Current number of busy XML threads: {1} Consecutive samples: {2} | |||||||
Target | XenApp | |||||||
Enabled by default | Yes |
Monitor State | Health State |
---|---|
OverThreshold | Warning |
UnderThreshold | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Threshold | 10 |
NumberOfSamples | 2 |
Display Name | XenApp Server Zone Elections Triggered | |||||||
---|---|---|---|---|---|---|---|---|
Description | Monitors the number of times this server has called for an election. This counter is incremented regardless of whether or not a new Zone Data Collector was elected. | |||||||
Knowledge Article |
SummaryThis monitor checks the number of times the XenApp server has called for an election in a specified time period. This counter is incremented regardless of whether or not a new Zone Data Collector was elected. By default, alert is generated if two zone elections are triggered on server in one hour. To modify the time period, override NumSamples parameter with the following formula: NumSamples = 3600 * <time interval in hours> / IntervalSeconds ConfigurationOverridable parameters:
CausesZone election can be triggered for many reasons:
Note: In XenApp 6.5 worker servers cannot trigger elections. AdditionalTo check the number of Zone Elections Triggered, open XenApp Server Performance view. To check if IMA service is being restarted frequently, search XenApp Server Closed Alerts for multiple "Windows Service Stopped" alerts with "The Citrix Independent Management Architecture service on computer <name> has stopped running." message. | |||||||
Alert Name | Zone Elections Triggered Too High | |||||||
Alert Message | Number of times the XenApp server ({0}) has called for an election in the last monitoring period has exceeded the threshold value. Current zone elections triggered: {1} | |||||||
Target | XenApp | |||||||
Enabled by default | Yes |
Monitor State | Health State |
---|---|
Elections triggered too high | Warning |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Threshold | 2 |
NumSamples | 12 |
Display Name | XenApp Server Load Full | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description | Checks if Citrix XenApp server load has reached 100%. | |||||||||||||
Knowledge Article |
SummaryMonitor checks server availability by checking server load. Server load is a value reported by the Citrix load evaluator that has been assigned to the server. If the load reaches 100% (load evaluator value = 10000) then users can no longer login to server. Load can be 100% because of the actual load on the server or because of the scheduled load evaluator rule (“Citrix Maintenance Mode”). In case the license cannot be obtained from license server, server load is 200% (load evaluator value = 20000). ConfigurationOverridable parameters:
Possible monitor states:
| |||||||||||||
Target | XenApp Availability | |||||||||||||
Enabled by default | Yes |
Monitor State | Health State |
---|---|
Available | Healthy |
InCitrixMaintenance | Warning |
FullLoad | Critical |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
TreatScheduledFullLoadAsMaintenance | true |
Display Name | XenApp MP Agent Installation | |
---|---|---|
Description | Monitors whether the Citrix XenApp MP Agent is installed on a server. | |
Knowledge Article |
SummaryAlerts if the Citrix XenApp MP Agent has not been deployed to the XenApp server. This is very useful in situations when you are not sure whether a specific XenApp server has been put under control of the XenApp MP or not. | |
Alert Name | XenApp MP Agent Installation | |
Alert Message | Citrix XenApp MP Agent on '{0}' is not installed! | |
Target | XenApp Computer Role | |
Enabled by default | Yes |
Monitor State | Health State |
---|---|
XenAppMPAgentInstalled | Healthy |
XenAppMPAgentNotInstalled | Warning |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp ICA Port - Connection Refused | |
---|---|---|
Description | Monitors if the connection to a port was forcibly closed. | |
Knowledge Article |
SummaryAlerts if connection to the ICA listener port was refused. Probing is executed from the MS Operations Manager server’s perspective. ICA clients typically connect to the XenApp server via this port. Inability to connect means that end-users are also not going to be able to connect to this system. | |
Alert Name | XenApp ICA Port - Connection Refused | |
Alert Message | No connection could be made because the target machine actively refused it. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp ICA Port - Connection TimeOut | |
---|---|---|
Description | Monitors timeouts when connection attempts to a port are performed. | |
Knowledge Article |
SummaryAlerts if connecting to the ICA listener port timed-out. Probing is executed from the MS Operations Manager server’s perspective. ICA clients typically connect to the XenApp server via this port. Inability to connect means that end-users are also not going to be able to connect to this system. | |
Alert Name | XenApp ICA Port - Connection TimeOut | |
Alert Message | A connection attempt failed because the connected party did not properly respond after a period of time, or an established connection failed because the connected host has failed to respond. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp ICA Port - DNS Resolution Failure | |
---|---|---|
Description | Monitors for any DNS resolution failure when attempting to connect to a port. | |
Knowledge Article |
SummaryAlerts if connection to the ICA listener port failed due to inability to resolve DNS name of the XenApp server to IP address. Probing is executed from the MS Operations Manager server’s perspective. ICA clients typically connect to the XenApp server via this port. Inability to connect means that end-users are also not going to be able to connect to this system. | |
Alert Name | XenApp ICA Port - DNS Resolution Failure | |
Alert Message | Unable to resolve name to IP. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp ICA Port - Host Unreachable | |
---|---|---|
Description | Monitors situations when the connection to a port is not possible because of an unreachable host. | |
Knowledge Article |
SummaryAlerts if connection to the ICA listener port failed due to the host being unreachable. Probing is executed from the MS Operations Manager server’s perspective. ICA clients typically connect to the XenApp server via this port. Inability to connect means that end-users are also not going to be able to connect to this system. | |
Alert Name | XenApp ICA Port - Host Unreachable | |
Alert Message | A socket operation was attempted to an unreachable host. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp IMA Port - Connection Refused | |
---|---|---|
Description | Monitors if the connection to a port was being forcibly closed. | |
Knowledge Article |
SummaryAlerts if connection to the IMA service port was refused. Probing is executed from the MS Operations Manager server’s perspective. IMA service keeps the farm together. If the IMA service stops responding, the server is marked as "offline" by the rest of the XenApp farm. | |
Alert Name | XenApp IMA Port - Connection Refused | |
Alert Message | No connection could be made because the target machine actively refused it. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp IMA Port - Connection TimeOut | |
---|---|---|
Description | Monitors timeouts when connection attempts to a port are performed. | |
Knowledge Article |
SummaryAlerts if connection to the IMA service port timed-out. Probing is executed from the MS Operations Manager server’s perspective. IMA service keeps the farm together. If the IMA service stops responding, the server is marked as "offline" by the rest of the XenApp farm. | |
Alert Name | XenApp IMA Port - Connection TimeOut | |
Alert Message | A connection attempt failed because the connected party did not properly respond after a period of time, or an established connection failed because connected host has failed to respond. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp IMA Port - DNS Resolution Failure | |
---|---|---|
Description | Monitors for any DNS resolution failure when attempting to connect to a port. | |
Knowledge Article |
SummaryAlerts if connection to the IMA service port failed due to inability to resolve DNS name of the XenApp server to IP address. Probing is executed from the MS Operations Manager server’s perspective. IMA service keeps the farm together. If the IMA service stops responding, the server is marked as "offline" by the rest of the XenApp farm. | |
Alert Name | XenApp IMA Port - DNS Resolution Failure | |
Alert Message | Unable to resolve name to IP. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp IMA Port - Host Unreachable | |
---|---|---|
Description | Monitors situations when the connection to a port is not possible because of an unreachable host. | |
Knowledge Article |
SummaryAlerts if connecting to the IMA service port failed due to the host being unreachable. Probing is executed from the MS Operations Manager server’s perspective. IMA service keeps the farm together. If IMA service stops responding, the server is marked as "offline" by the rest of the XenApp farm. | |
Alert Name | XenApp IMA Port - Host Unreachable | |
Alert Message | A socket operation was attempted to an unreachable host. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp Management Console Port - Connection Refused | |
---|---|---|
Description | Monitors if the connection to a port was forcibly closed. | |
Knowledge Article |
SummaryAlerts if connection to the Management Console port was refused. Probing is executed from the MS Operations Manager server’s perspective. This is the port the Citrix Management Console connects to. It is not that critical if this server is not used for console’s connection. | |
Alert Name | XenApp Management Console Port - Connection Refused | |
Alert Message | No connection could be made because the target machine actively refused it. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp Management Console Port - Connection TimeOut | |
---|---|---|
Description | Monitors timeouts when connection attempts to a port are performed. | |
Knowledge Article |
SummaryAlerts if connection to the Management Console port timed-out. Probing is executed from the MS Operations Manager server’s perspective. This is the port the Citrix Management Console connects to. It is not that critical if this server is not used for console’s connection. | |
Alert Name | XenApp Management Console Port - Connection TimeOut | |
Alert Message | A connection attempt failed because the connected party did not properly respond after a period of time, or an established connection failed because connected host has failed to respond. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp Management Console Port - DNS Resolution Failure | |
---|---|---|
Description | Monitors for any DNS resolution failure when attempting to connect to a port. | |
Knowledge Article |
SummaryAlerts if connection to the Management Console port failed due to inability to resolve DNS name of the XenApp server to IP address. Probing is executed from the MS Operations Manager server’s perspective. This is the port the Citrix Management Console connects to. It is not that critical if this server is not used for console’s connection. | |
Alert Name | XenApp Management Console Port - DNS Resolution Failure | |
Alert Message | Unable to resolve name to IP. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp Management Console Port - Host Unreachable | |
---|---|---|
Description | Monitors situations when the connection to a port is not possible because of an unreachable host. | |
Knowledge Article |
SummaryAlerts if connection to the Management Console port failed due to the host being unreachable. Probing is executed from the MS Operations Manager server’s perspective. This is the port the Citrix Management Console connects to. It is not that critical if this server is not used for console’s connection. | |
Alert Name | XenApp Management Console Port - Host Unreachable | |
Alert Message | A socket operation was attempted to an unreachable host. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp RDP Port - Connection Refused | |
---|---|---|
Description | Monitors if the connection to a port was forcibly closed. | |
Knowledge Article |
SummaryAlerts if connection to the RDP listener port was refused. Probing is executed from the MS Operations Manager server’s perspective. This is the port the Terminal Services clients (Remote Desktop Connection clients) connect to. If this port is not reachable, RDP clients cannot connect to the server. | |
Alert Name | XenApp RDP Port - Connection Refused | |
Alert Message | No connection could be made because the target machine actively refused it. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp RDP Port - Connection TimeOut | |
---|---|---|
Description | Monitors timeouts when connection attempts to a port are performed. | |
Knowledge Article |
SummaryAlerts if connection to the RDP listener port timed-out. Probing is executed from the MS Operations Manager server’s perspective. This is the port the Terminal Services clients (Remote Desktop Connection clients) connect to. If this port is not reachable, RDP clients cannot connect to the server. | |
Alert Name | XenApp RDP Port - Connection TimeOut | |
Alert Message | A connection attempt failed because the connected party did not properly respond after a period of time, or an established connection failed because connected host has failed to respond. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp RDP Port - DNS Resolution Failure | |
---|---|---|
Description | Monitors for any DNS resolution failure when attempting to connect to a port. | |
Knowledge Article |
SummaryAlerts if connection to the RDP listener port failed due to inability to resolve DNS name of the XenApp server to IP address. Probing is executed from the MS Operations Manager server’s perspective. This is the port the Terminal Services clients (Remote Desktop Connection clients) connect to. If this port is not reachable, RDP clients cannot connect to the server. | |
Alert Name | XenApp RDP Port - DNS Resolution Failure | |
Alert Message | Unable to resolve name to IP. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp RDP Port - Host Unreachable | |
---|---|---|
Description | Monitors situations when the connection to a port is not possible because of an unreachable host. | |
Knowledge Article |
SummaryAlerts if connection to the RDP listener port failed due to the host being unreachable. Probing is executed from the MS Operations Manager server’s perspective. This is the port the Terminal Services clients (Remote Desktop Connection clients) connect to. If this port is not reachable, RDP clients cannot connect to the server. | |
Alert Name | XenApp RDP Port - Host Unreachable | |
Alert Message | A socket operation was attempted to an unreachable host. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp Session Reliability Port - Connection Refused | |
---|---|---|
Description | Monitors if the connection to a port was forcibly closed. | |
Knowledge Article |
SummaryAlerts if connection to the Session Reliability port was refused. Probing is executed from the MS Operations Manager server’s perspective. This is a proxy port/service for the ICA port. Session reliability allows quick reconnect to a Citrix session if a connection was lost for a short period of time. | |
Alert Name | XenApp Session Reliability Port - Connection Refused | |
Alert Message | No connection could be made because the target machine actively refused it. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp Session Reliability Port - Connection TimeOut | |
---|---|---|
Description | Monitors timeouts when connection attempts to a port are performed. | |
Knowledge Article |
SummaryAlerts if connection to the Session Reliability port timed-out. Probing is executed from the MS Operations Manager server’s perspective. This is a proxy port/service for the ICA port. Session reliability allows quick reconnect to a Citrix session if a connection was lost for a short period of time. | |
Alert Name | XenApp Session Reliability Port - Connection TimeOut | |
Alert Message | A connection attempt failed because the connected party did not properly respond after a period of time, or an established connection failed because connected host has failed to respond. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp Session Reliability Port - DNS Resolution Failure | |
---|---|---|
Description | Monitors for any DNS resolution failure when attempting to connect to a port. | |
Knowledge Article |
SummaryAlerts if connection to the Session Reliability port failed due to inability to resolve DNS name of the XenApp server to IP address. Probing is executed from the MS Operations Manager server’s perspective. This is a proxy port/service for the ICA port. Session reliability allows quick reconnect to a Citrix session if a connection was lost for a short period of time. | |
Alert Name | XenApp Session Reliability Port - DNS Resolution Failure | |
Alert Message | Unable to resolve name to IP. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp Session Reliability Port - Host Unreachable | |
---|---|---|
Description | Monitors situations when the connection to a port is not possible because of an unreachable host. | |
Knowledge Article |
SummaryAlerts if connection to the Session Reliability port failed due to the host being unreachable. Probing is executed from the MS Operations Manager server’s perspective. This is a proxy port/service for the ICA port. Session reliability allows quick reconnect to a Citrix session if a connection was lost for a short period of time. | |
Alert Name | XenApp Session Reliability Port - Host Unreachable | |
Alert Message | A socket operation was attempted to an unreachable host. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp XML Service Port - Connection Refused | |
---|---|---|
Description | Monitors for the connection to a port being forcibly closed. | |
Knowledge Article |
SummaryAlerts if connection to the XML Service port was refused. Probing is executed from the MS Operations Manager server’s perspective. This service is used for Web Interface – XenApp server communication. Mostly, just those XenApp servers that are configured as brokers for the Web Interface are critical. | |
Alert Name | XenApp XML Service Port - Connection Refused | |
Alert Message | No connection could be made because the target machine actively refused it. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp XML Service Port - Connection TimeOut | |
---|---|---|
Description | Monitors timeouts when connection attempts to a port are performed. | |
Knowledge Article |
SummaryAlerts if connection to the XML Service port timed-out. Probing is executed from the MS Operations Manager server’s perspective. This service is used for Web Interface – XenApp server communication. Mostly, just those XenApp servers that are configured as brokers for the Web Interface are critical. | |
Alert Name | XenApp XML Service Port - Connection TimeOut | |
Alert Message | A connection attempt failed because the connected party did not properly respond after a period of time, or an established connection failed because connected host has failed to respond. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp XML Service Port - DNS Resolution Failure | |
---|---|---|
Description | Monitors for any DNS resolution failure when attempting to connect to a port. | |
Knowledge Article |
SummaryAlerts if connection to the XML Service port failed due to inability to resolve DNS name of the XenApp server to IP address. Probing is executed from the MS Operations Manager server’s perspective. This service is used for Web Interface – XenApp server communication. Mostly, just those XenApp servers that are configured as brokers for the Web Interface are critical. | |
Alert Name | XenApp XML Service Port - DNS Resolution Failure | |
Alert Message | Unable to resolve name to IP. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp XML Service Port - Host Unreachable | |
---|---|---|
Description | Monitors situations when the connection to a port is not possible because of an unreachable host. | |
Knowledge Article |
SummaryAlerts if connecting to the XML Service port failed due to the host being unreachable. Probing is executed from the MS Operations Manager server’s perspective. This service is used for Web Interface – XenApp server communication. Mostly, just those XenApp servers that are configured as brokers for the Web Interface are critical. | |
Alert Name | XenApp XML Service Port - Host Unreachable | |
Alert Message | A socket operation was attempted to an unreachable host. ServerName: {0} Port: {1} | |
Target | XenApp TCP Probe | |
Enabled by default | No |
Monitor State | Health State |
---|---|
Error | Critical |
OK | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 3600 |
Port | -- defined with discovered object property -- |
Display Name | XenApp Zone Off-line Servers | |
---|---|---|
Description | Monitors the number of off-line servers in a XenApp zone. | |
Knowledge Article |
SummaryAlerts if a large number of XenApp servers becomes unavailable in a zone. This typically indicates larger outage of XenApp farm’s capacity, and can be attributed to the network connectivity loss, or to a massive server shutdown / power failure. | |
Alert Name | XenApp Zone Off-line Servers | |
Alert Message | Number of off-line servers in "{0}" zone has exceeded the threshold value. Off-line servers: {1} | |
Target | Zone Data Collector | |
Enabled by default | No |
Monitor State | Health State |
---|---|
GreaterThanEqualThreshold | Warning |
LessThanThreshold | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
ThresholdValue | 10 |
Display Name | XenApp Zone Off-line Servers Percentage | |
---|---|---|
Description | Monitors the percentage of off-line servers in a XenApp zone. | |
Knowledge Article |
SummaryAlerts if a large % of XenApp servers becomes unavailable in a zone. This typically indicates a larger outage of XenApp farm’s capacity, and can be attributed to the network connectivity loss, or to a massive server shutdown / power failure. | |
Alert Name | XenApp Zone Off-line Servers Percentage | |
Alert Message | Percentage of off-line servers in "{0}" zone has exceeded the threshold value. Off-line servers percentage: {1}% | |
Target | Zone Data Collector | |
Enabled by default | Yes |
Monitor State | Health State |
---|---|
GreaterThanEqualCriticalThreshold | Critical |
GreaterThanEqualWarningThreshold | Warning |
LessThanWarningThreshold | Healthy |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
ThresholdCriticalValue | 100 |
ThresholdWarningValue | 70 |
Display Name | Custom File Count of User Profile (Alert) | |
---|---|---|
Description | Monitors the custom file count of a user profile. | |
Knowledge Article |
SummaryHelps to identify user profiles that contain custom file category. This can be configured to any specific set of file extensions as needed. | |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | Custom File Count of User Profile | |
Alert Message | Custom file count of the user profile exceeded the threshold value. Custom file count: {0} User profile info: Measurement time: {1} Domain name: {2} Username: {3} Total file size: {4} MB Total file count: {5} Custom file count: {6} Executable file count: {7} Media file count: {8} For more information about user profile see Alert Context section. |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Threshold | 1 |
Priority | 1 |
Severity | 2 |
Display Name | Executable File Count of User Profile (Alert) | |
---|---|---|
Description | Monitors the executable file count of a user profile. | |
Knowledge Article |
SummaryHelps to identify user profiles that contain executable files. User profiles should normally not contain any executable files. | |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | Executable File Count of User Profile | |
Alert Message | Executable file count of the user profile exceeded the threshold value. Executable file count: {0} User profile info: Measurement time: {1} Domain name: {2} Username: {3} Total file size: {4} MB Total file count: {5} Custom file count: {6} Executable file count: {7} Media file count: {8} For more information about user profile see Alert Context section. |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Threshold | 1 |
Priority | 1 |
Severity | 2 |
Display Name | Media File Count of User Profile (Alert) | |
---|---|---|
Description | Monitors the media file count of a user profile. | |
Knowledge Article |
SummaryHelps to identify user profiles that contain media files (mp3s, movies, etc.). User profiles should normally not contain any large media files. | |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | Media File Count of User Profile | |
Alert Message | Media file count of the user profile exceeded the threshold value. Media file count: {0} User profile info: Measurement time: {1} Domain name: {2} Username: {3} Total file size: {4} MB Total file count: {5} Custom file count: {6} Executable file count: {7} Media file count: {8} For more information about user profile see Alert Context section. |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Threshold | 1 |
Priority | 1 |
Severity | 2 |
Display Name | Total File Count of User Profile (Alert) | |
---|---|---|
Description | Monitors the total file count of a user profile. | |
Knowledge Article |
SummaryHelps to identify user profiles that contain a large number of files. With roaming profiles, a large number of files in a user’s profile means that user’s logon and logoff processes are going to be slower. | |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | Total File Count of User Profile | |
Alert Message | Total file count of the user profile exceeded the threshold value. Total file count: {0} User profile info: Measurement time: {1} Domain name: {2} Username: {3} Total file size: {4} MB Total file count: {5} Custom file count: {6} Executable file count: {7} Media file count: {8} For more information about user profile see Alert Context section. |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Threshold | 5000 |
Priority | 1 |
Severity | 2 |
Display Name | Total File Size of User Profile (Alert) | |
---|---|---|
Description | Monitors the total file size of a user profile. | |
Knowledge Article |
SummaryHelps to identify user profiles that are very large. With roaming profiles, a large user’s profile means that user’s logon and logoff processes are going to be slower. | |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | Total File Size of User Profile | |
Alert Message | Total file size of the user profile exceeded the threshold value. Total file size: {0} MB User profile info: Measurement time: {1} Domain name: {2} Username: {3} Total file size: {4} MB Total file count: {5} Custom file count: {6} Executable file count: {7} Media file count: {8} For more information about user profile see Alert Context section. |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Threshold | 1000 |
Priority | 1 |
Severity | 2 |
Display Name | User Logon Process - Applying GPOs (Phase 2) Duration (Alert) | |
---|---|---|
Description | Monitors the duration of the applying group policies phase of the user logon process. | |
Knowledge Article |
SummaryHelps to identify a user whose logon process – phase 2 (applying Group Policy Objects) was very slow. During this phase the server applies user settings defined on the Domain Controller. ConfigurationOverridable parameters:
CausesReasons for a slow logon phase can be:
| |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | User Logon Process - Applying GPOs (Phase 2) Duration | |
Alert Message | The duration of the applying group policies phase of the user logon process exceeded the threshold value. Applying GPOs (Phase 2) duration: {0} seconds Logon info: Logon time: {1} Session ID: {2} Domain: {3} Username: {4} Client name: {5} Type: {6} Complete logon duration: {7} seconds |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CriticalThreshold | 240 |
WarningThreshold | 180 |
InfoThreshold | 120 |
Priority | 1 |
Severity | -- defined with discovered object property -- |
Display Name | User Logon Process - Citrix initialization (Phase 5) Duration (Alert) | |
---|---|---|
Description | Monitors the duration of the Citrix initialization phase of the user logon process. | |
Knowledge Article |
SummaryHelps to identify a user whose logon process – phase 5 (Citrix-specific initialization phase) was very slow. This phase covers Citrix specific activity before it launches the requested application: launching seamless windows engine shell, auto creation of client printers and ICA client update process. ConfigurationOverridable parameters:
CausesReasons for a slow logon phase can be:
| |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | User Logon Process - Citrix initialization (Phase 5) Duration | |
Alert Message | The duration of the Citrix initialization phase of the user logon process exceeded the threshold value. Citrix initialization (Phase 5) duration: {0} seconds Logon info: Logon time: {1} Session ID: {2} Domain: {3} Username: {4} Client name: {5} Type: {6} Complete logon duration: {7} seconds |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CriticalThreshold | 240 |
WarningThreshold | 180 |
InfoThreshold | 120 |
Priority | 1 |
Severity | -- defined with discovered object property -- |
Display Name | User Logon Process - Complete Duration (Alert) | |
---|---|---|
Description | Monitors the duration of the complete user logon process. | |
Knowledge Article |
SummaryHelps to identify a user whose logon process was very slow. It provides also information about duration for each logon phase. ConfigurationOverridable parameters:
AdditionalUser logon is a complex and resource intensive process on a Citrix XenApp server. It is initiated when Citrix farm load balancing algorithm selects the system where published application that user has selected will be started, and ends when the application is running and the user is able to interact with it. XenApp Management Pack breaks down the logon process on a Citrix XenApp server into five phases. Phase 1: User profile loading The phase starts just after the user credentials are validated and lasts until the profile is downloaded from the profile storage (network share). Phase 2: Applying group policy objects (GPOs) During this phase the server applies user settings defined on the Domain Controller. Phase 3: User environment initialization and Active Setup During this phase network connections are restored and profile settings, such as fonts and screen colors, are loaded. Also, if this is the first time this profile is being used, some extra initialization is applied. The default profile is created, first time use settings are applied for the shell (Explorer), Internet Explorer, Office (particularly Outlook) and any other application that uses Active Setup. Phase 4: Logon script execution The phase is measured by how long the USRLOGON.CMD script (located in %SystemRoot%\system32) is being executed. The script’s original function is to address issues with legacy applications that were not written with a multi-user environment, such as Terminal Server. It uses application compatibility scripts (located in %SystemRoot%\Application Compatibility Scripts) in conjunction with the %ROOTDRIVE% variable to address these issues. USRLOGON.CMD script is also used as a starting point for custom profile frameworks (i.e. not supported by Microsoft), such as Flex or Jumping profiles. Phase 5: Citrix Application initialization The phase covers Citrix specific activity before it launches the requested application: launching seamless windows engine shell, auto creation of client printers and ICA client update process. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | Alert | |
Generate Alert | True | |
Alert Name | User Logon Process - Complete Duration | |
Alert Message | The duration of the complete user logon process exceeded the threshold value. Complete logon duration: {0} seconds Phases duration in seconds: {1} Logon info: Logon time: {2} Session ID: {3} Domain: {4} Username: {5} Client name: {6} Type: {7} |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CriticalThreshold | 240 |
WarningThreshold | 180 |
InfoThreshold | 120 |
Priority | 1 |
Severity | -- defined with discovered object property -- |
Display Name | User Logon Process - Completed Phases (Alert) | |
---|---|---|
Description | Monitors whether all phases of the user logon process on the XenApp server have completed successfully. | |
Knowledge Article |
SummaryHelps to identify a user whose logon process failed or was timed out after 5 minutes. It also provides information on which phase of the logon process was responsible for the failure/timeout. ConfigurationOverridable parameters:
AdditionalUser logon is a complex and resource intensive process on a Citrix XenApp server. It is initiated when Citrix farm load balancing algorithm selects the system where published application that user has selected will be started, and ends when the application is running and the user is able to interact with it. XenApp Management Pack breaks down the logon process on a Citrix XenApp server into five phases. Phase 1: User profile loading The phase starts just after the user credentials are validated and lasts until the profile is downloaded from the profile storage (network share). Phase 2: Applying group policy objects (GPOs) During this phase the server applies user settings defined on the Domain Controller. Phase 3: User environment initialization and Active Setup During this phase network connections are restored and profile settings, such as fonts and screen colors, are loaded. Also, if this is the first time this profile is being used, some extra initialization is applied. The default profile is created, first time use settings are applied for the shell (Explorer), Internet Explorer, Office (particularly Outlook) and any other application that uses Active Setup. Phase 4: Logon script execution The phase is measured by how long the USRLOGON.CMD script (located in %SystemRoot%\system32) is being executed. The script’s original function is to address issues with legacy applications that were not written with a multi-user environment, such as Terminal Server. It uses application compatibility scripts (located in %SystemRoot%\Application Compatibility Scripts) in conjunction with the %ROOTDRIVE% variable to address these issues. USRLOGON.CMD script is also used as a starting point for custom profile frameworks (i.e. not supported by Microsoft), such as Flex or Jumping profiles. Phase 5: Citrix Application initialization The phase covers Citrix specific activity before it launches the requested application: launching seamless windows engine shell, auto creation of client printers and ICA client update process. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | Alert | |
Generate Alert | True | |
Alert Name | User Logon Process - Completed Phases | |
Alert Message | All phases of the user logon process have not completed successfully. {0} Completed phases: {1} Phases duration in seconds: {2} Logon info: Logon time: {3} Session ID: {4} Domain: {5} Username: {6} Client name: {7} Type: {8} |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Threshold | 5 |
IgnoreTerminatedLogons | false |
Priority | 1 |
Severity | -- defined with discovered object property -- |
Display Name | User Logon Process - Logon script (Phase 4) Duration (Alert) | |
---|---|---|
Description | Monitors the duration of the loading user scripts phase of the user logon process. | |
Knowledge Article |
SummaryHelps to identify a user whose logon process – phase 4 (logon script execution phase) was very slow. The phase is measured by how long the USRLOGON.CMD script (located in %SystemRoot%\system32) is being executed. The script’s original function is to address issues with legacy applications that were not written with a multi-user environment, such as Terminal Server. It uses application compatibility scripts (located in %SystemRoot%\Application Compatibility Scripts) in conjunction with the %ROOTDRIVE% variable to address these issues. USRLOGON.CMD script is also used as a starting point for custom profile frameworks (i.e. not supported by Microsoft), such as Flex or Jumping profiles. ConfigurationOverridable parameters:
CausesReasons for a slow logon phase can be:
| |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | User Logon Process - Logon script (Phase 4) Duration | |
Alert Message | The duration of the loading user scripts phase of the user logon process exceeded the threshold value. Logon script (Phase 4) duration: {0} seconds Logon info: Logon time: {1} Session ID: {2} Domain: {3} Username: {4} Client name: {5} Type: {6} Complete logon duration: {7} seconds |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CriticalThreshold | 240 |
WarningThreshold | 180 |
InfoThreshold | 120 |
Priority | 1 |
Severity | -- defined with discovered object property -- |
Display Name | User Logon Process - Profile loading (Phase 1) Duration (Alert) | |
---|---|---|
Description | Monitors the duration of the user profile loading phase of the user logon process. | |
Knowledge Article |
SummaryHelps to identify a user whose logon process – phase 1 (profile loading phase) was very slow. The phase starts just after the user credentials are validated and lasts until the profile is downloaded from the profile storage (network share). ConfigurationOverridable parameters:
CausesReasons for a slow logon phase can be:
| |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | User Logon Process - Profile loading (Phase 1) Duration | |
Alert Message | The duration of the user profile loading phase of the user logon process exceeded the threshold value. Profile loading (Phase 1) duration: {0} seconds Logon info: Logon time: {1} Session ID: {2} Domain: {3} Username: {4} Client name: {5} Type: {6} Complete logon duration: {7} seconds |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CriticalThreshold | 240 |
WarningThreshold | 180 |
InfoThreshold | 120 |
Priority | 1 |
Severity | -- defined with discovered object property -- |
Display Name | User Logon Process - User initialization (Phase 3) Duration (Alert) | |
---|---|---|
Description | Monitors the duration of the user initialization phase of the user logon process. | |
Knowledge Article |
SummaryHelps to identify a user whose logon process – phase 3 (User-specific Initialization) was very slow. During this phase network connections are restored and profile settings, such as fonts and screen colors, are loaded. Also, if this is the first time this profile is being used, some extra initialization is applied. The default profile is created, first time use settings are applied for the shell (Explorer), Internet Explorer, Office (particularly Outlook) and any other application that uses Active Setup. ConfigurationOverridable parameters:
CausesReasons for a slow logon phase can be:
| |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | User Logon Process - User initialization (Phase 3) Duration | |
Alert Message | The duration of the user initialization phase of the user logon process exceeded the threshold value. User initialization (Phase 3) duration: {0} seconds Logon info: Logon time: {1} Session ID: {2} Domain: {3} Username: {4} Client name: {5} Type: {6} Complete logon duration: {7} seconds |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CriticalThreshold | 240 |
WarningThreshold | 180 |
InfoThreshold | 120 |
Priority | 1 |
Severity | -- defined with discovered object property -- |
Display Name | XenApp Process CPU Usage (Alert) | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description | Monitors high CPU usage for processes on XenApp server. | |||||||||||||||
Knowledge Article |
SummaryCPU utilization for process on XenApp server is high. ConfigurationThe following configuration parameters are customizable:
CollectionType parameter options:
| |||||||||||||||
Target | XenApp | |||||||||||||||
Enabled by default | No | |||||||||||||||
Category | Alert | |||||||||||||||
Generate Alert | True | |||||||||||||||
Alert Name | XenApp Process CPU Usage | |||||||||||||||
Alert Message | Process CPU usage exceeded the threshold value. XenApp server: {0} {1} CPU usage: {2} % Time sampled: {3} |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CollectionType | TOP CPU 10 |
Threshold | 95 |
NumberOfSamples | 3 |
Priority | 1 |
Severity | 2 |
Display Name | XenApp Process IO Operations (Alert) | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description | Monitors high IO operations per second for processes on XenApp server. | |||||||||||||||
Knowledge Article |
SummaryIO Operations per second for process on XenApp server is high. ConfigurationThe following configuration parameters are customizable:
CollectionType parameter options:
| |||||||||||||||
Target | XenApp | |||||||||||||||
Enabled by default | No | |||||||||||||||
Category | Alert | |||||||||||||||
Generate Alert | True | |||||||||||||||
Alert Name | XenApp Process IO Operations | |||||||||||||||
Alert Message | Process IO operations per second exceeded the threshold value. XenApp server: {0} {1} IO operations per second: {2} Time sampled: {3} |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CollectionType | TOP CPU 10 |
Threshold | 1000 |
NumberOfSamples | 3 |
Priority | 1 |
Severity | 2 |
Display Name | XenApp Process Page Faults (Alert) | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description | Monitors high Page Faults per second for processes on XenApp server. | |||||||||||||||
Knowledge Article |
SummaryPage Faults per second for process on XenApp server is high. ConfigurationThe following configuration parameters are customizable:
CollectionType parameter options:
| |||||||||||||||
Target | XenApp | |||||||||||||||
Enabled by default | No | |||||||||||||||
Category | Alert | |||||||||||||||
Generate Alert | True | |||||||||||||||
Alert Name | XenApp Process Page Faults | |||||||||||||||
Alert Message | Process Page faults per second exceeded the threshold value. XenApp server: {0} {1} Page faults per second: {2} Time sampled: {3} |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CollectionType | TOP CPU 10 |
Threshold | 5000 |
NumberOfSamples | 3 |
Priority | 1 |
Severity | 2 |
Display Name | XenApp Process Page File Size (Alert) | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description | Monitors high Page File Size for processes on XenApp server. | |||||||||||||||
Knowledge Article |
SummaryPage file size for process on XenApp server is high. ConfigurationThe following configuration parameters are customizable:
CollectionType parameter options:
| |||||||||||||||
Target | XenApp | |||||||||||||||
Enabled by default | No | |||||||||||||||
Category | Alert | |||||||||||||||
Generate Alert | True | |||||||||||||||
Alert Name | XenApp Process Page File Size | |||||||||||||||
Alert Message | Process Page file size exceeded the threshold value. XenApp server: {0} {1} Page file size: {2} MB Time sampled: {3} |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CollectionType | TOP CPU 10 |
Threshold | 1024 |
NumberOfSamples | 3 |
Priority | 1 |
Severity | 2 |
Display Name | XenApp Process Working Set Size (Alert) | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description | Monitors high Working set size for processes on XenApp server. | |||||||||||||||
Knowledge Article |
SummaryWorking set size for process on XenApp server is high. ConfigurationThe following configuration parameters are customizable:
CollectionType parameter options:
| |||||||||||||||
Target | XenApp | |||||||||||||||
Enabled by default | No | |||||||||||||||
Category | Alert | |||||||||||||||
Generate Alert | True | |||||||||||||||
Alert Name | XenApp Process Working Set Size | |||||||||||||||
Alert Message | Process Working set size exceeded the threshold value. XenApp server: {0} {1} Working set size: {2} MB Time sampled: {3} |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CollectionType | TOP CPU 10 |
Threshold | 1024 |
NumberOfSamples | 3 |
Priority | 1 |
Severity | 2 |
Display Name | XenApp Session CPU Utilization (Alert) | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | Monitors the CPU utilization of a session. | |||||||||
Knowledge Article |
SummaryHelps to identify sessions that host CPU hungry applications. The name of the user, application, and client IP address are included in the alert details. Alert is triggered only when CPU usage is above threshold for specified number of consecutive samples (NumberOfSamples parameter). ConfigurationThe following configuration parameters are customizable:
Formula for ConsolidationInterval: ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1 Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples): IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990 | |||||||||
Target | XenApp | |||||||||
Enabled by default | Yes | |||||||||
Category | Alert | |||||||||
Generate Alert | True | |||||||||
Alert Name | XenApp Session CPU Utilization | |||||||||
Alert Message | CPU utilization of a session on {0} is above the threshold for multiple consecutive samples. CPU utilization: {1} % Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
NumberOfSamples | 3 |
IntervalSeconds | 300 |
Threshold | 90 |
ConsolidationInterval | 660 |
Priority | 1 |
Severity | 1 |
Display Name | XenApp Session CPU Utilization (non consecutive) (Alert) | |
---|---|---|
Description | Monitors the CPU utilization of a session. | |
Knowledge Article |
SummaryHelps to identify sessions that host CPU hungry applications. The name of the user, application, and client IP address are included in the alert details. This monitor is disabled by default because consecutive samples counterpart rule is enabled by default. | |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | XenApp Session CPU Utilization | |
Alert Message | CPU utilization of a session on {0} exceeded the threshold value. CPU utilization: {1} % Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CriticalThreshold | 90 |
WarningThreshold | 70 |
Priority | 1 |
Severity | -- defined with discovered object property -- |
Display Name | XenApp Session Handle Count (Alert) | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | Monitors the handle count of a session. | |||||||||
Knowledge Article |
SummaryHelps to identify sessions that host applications that are very likely leaking kernel handles. This can potentially lead to an unstable session. The name of the user, application, and client IP address are included in the alert details. Alert is triggered only when handle count is above threshold for specified number of consecutive samples (NumberOfSamples parameter). ConfigurationThe following configuration parameters are customizable:
Formula for ConsolidationInterval: ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1 Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples): IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990 | |||||||||
Target | XenApp | |||||||||
Enabled by default | No | |||||||||
Category | Alert | |||||||||
Generate Alert | True | |||||||||
Alert Name | XenApp Session Handle Count | |||||||||
Alert Message | Handle count of a session on {0} is above the threshold for multiple consecutive samples. Handle count: {1} Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
NumberOfSamples | 3 |
IntervalSeconds | 300 |
Threshold | 60000 |
ConsolidationInterval | 660 |
Priority | 1 |
Severity | 1 |
Display Name | XenApp Session Handle Count (non consecutive) (Alert) | |
---|---|---|
Description | Monitors the handle count of a session. | |
Knowledge Article |
SummaryHelps to identify sessions that host applications that are very likely leaking kernel handles. This can potentially lead to an unstable session. The name of the user, application, and client IP address are included in the alert details. This monitor is disabled by default because consecutive samples counterpart rule is enabled by default. | |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | XenApp Session Handle Count | |
Alert Message | Handle count of a session on {0} exceeded the threshold value. Handle count: {1} Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CriticalThreshold | 60000 |
WarningThreshold | 40000 |
Priority | 1 |
Severity | -- defined with discovered object property -- |
Display Name | XenApp Session Latency - Average (Alert) | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | Monitors the average latency (in milliseconds) of a session. | |||||||||
Knowledge Article |
SummaryHelps to identify sessions that deliver slow responsiveness (screen updates) to end-users. The name of the user, application, and client IP address are included in the alert details. Alert is triggered only when average latency (in milliseconds) is above threshold for specified number of consecutive samples (NumberOfSamples parameter). ConfigurationThe following configuration parameters are customizable:
Formula for ConsolidationInterval: ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1 Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples): IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990 | |||||||||
Target | XenApp | |||||||||
Enabled by default | No | |||||||||
Category | Alert | |||||||||
Generate Alert | True | |||||||||
Alert Name | XenApp Session Latency - Average | |||||||||
Alert Message | Average latency of a session on {0} is above the threshold for multiple consecutive samples. Average latency: {1} ms Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
NumberOfSamples | 3 |
IntervalSeconds | 300 |
Threshold | 5000 |
ConsolidationInterval | 660 |
Priority | 1 |
Severity | 1 |
Display Name | XenApp Session Latency - Average (non consecutive) (Alert) | |
---|---|---|
Description | Monitors the average latency (in milliseconds) of a session. | |
Knowledge Article |
SummaryHelps to identify sessions that deliver slow responsiveness (screen updates) to end-users. The name of the user, application, and client IP address are included in the alert details. This monitor is disabled by default because consecutive samples counterpart rule is enabled by default. | |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | XenApp Session Latency - Average | |
Alert Message | Average latency of a session on {0} exceeded the threshold value. Average latency: {1} ms Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CriticalThreshold | 10000 |
WarningThreshold | 5000 |
Priority | 1 |
Severity | -- defined with discovered object property -- |
Display Name | XenApp Session Latency - Deviation (Alert) | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | Monitors the latency deviation (in milliseconds) of a session. | |||||||||
Knowledge Article |
SummaryHelps to identify sessions that have inconsistent responsiveness (screen updates). To an end-user, this can be even worse than slow responsiveness. The name of the user, application, and client IP address are included in the alert details. Alert is triggered only when latency deviation (in milliseconds) is above threshold for specified number of consecutive samples (NumberOfSamples parameter). ConfigurationThe following configuration parameters are customizable:
Formula for ConsolidationInterval: ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1 Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples): IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990 | |||||||||
Target | XenApp | |||||||||
Enabled by default | No | |||||||||
Category | Alert | |||||||||
Generate Alert | True | |||||||||
Alert Name | XenApp Session Latency - Deviation | |||||||||
Alert Message | Latency deviation of a session on {0} is above the threshold for multiple consecutive samples. Latency deviation: {1} ms Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
NumberOfSamples | 3 |
IntervalSeconds | 300 |
Threshold | 5000 |
ConsolidationInterval | 660 |
Priority | 1 |
Severity | 1 |
Display Name | XenApp Session Latency - Deviation (non consecutive) (Alert) | |
---|---|---|
Description | Monitors the latency deviation (in milliseconds) of a session. | |
Knowledge Article |
SummaryHelps to identify sessions that have inconsistent responsiveness (screen updates). To an end-user, this can be even worse than slow responsiveness. The name of the user, application, and client IP address are included in the alert details. This monitor is disabled by default because consecutive samples counterpart rule is enabled by default. | |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | XenApp Session Latency - Deviation | |
Alert Message | Latency deviation of a session on {0} exceeded the threshold value. Latency deviation: {1} ms Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CriticalThreshold | 10000 |
WarningThreshold | 5000 |
Priority | 1 |
Severity | -- defined with discovered object property -- |
Display Name | XenApp Session Latency - Last Recorded (Alert) | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | Monitors the last recorded latency (in milliseconds) of a session. | |||||||||
Knowledge Article |
SummaryHelps to identify sessions that have just started to deliver slow responsiveness (screen updates) to end-users. The name of the user, application, and client IP address are included in the alert details. Alert is triggered only when last recorded latency (in milliseconds) is above threshold for specified number of consecutive samples (NumberOfSamples parameter). ConfigurationThe following configuration parameters are customizable:
Formula for ConsolidationInterval: ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1 Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples): IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990 | |||||||||
Target | XenApp | |||||||||
Enabled by default | Yes | |||||||||
Category | Alert | |||||||||
Generate Alert | True | |||||||||
Alert Name | XenApp Session Latency - Last Recorded | |||||||||
Alert Message | Last recorded latency of a session on {0} is above the threshold for multiple consecutive samples. Last recorded latency: {1} ms Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
NumberOfSamples | 3 |
IntervalSeconds | 300 |
Threshold | 5000 |
ConsolidationInterval | 660 |
Priority | 1 |
Severity | 1 |
Display Name | XenApp Session Latency - Last Recorded (non consecutive) (Alert) | |
---|---|---|
Description | Monitors the last recorded latency (in milliseconds) of a session. | |
Knowledge Article |
SummaryHelps to identify sessions that have just started to deliver slow responsiveness (screen updates) to end-users. The name of the user, application, and client IP address are included in the alert details. This monitor is disabled by default because consecutive samples counterpart rule is enabled by default. | |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | XenApp Session Latency - Last Recorded | |
Alert Message | Last recorded latency of a session on {0} exceeded the threshold value. Last recorded latency: {1} ms Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CriticalThreshold | 20000 |
WarningThreshold | 10000 |
Priority | 1 |
Severity | -- defined with discovered object property -- |
Display Name | XenApp Session Network Errors (Alert) | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | Monitors the network errors of a session. | |||||||||
Knowledge Article |
SummaryAlert is triggered only when number of network errors is above threshold for specified number of consecutive samples (NumberOfSamples parameter). ConfigurationThe following configuration parameters are customizable:
Formula for ConsolidationInterval: ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1 Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples): IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990 | |||||||||
Target | XenApp | |||||||||
Enabled by default | Yes | |||||||||
Category | Alert | |||||||||
Generate Alert | True | |||||||||
Alert Name | XenApp Session Network Errors | |||||||||
Alert Message | Network errors of a session on {0} is above the threshold for multiple consecutive samples. Total errors per second transferred: {1} Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
NumberOfSamples | 3 |
IntervalSeconds | 300 |
Threshold | 20 |
ConsolidationInterval | 660 |
Priority | 1 |
Severity | 1 |
Display Name | XenApp Session Network Errors (non consecutive) (Alert) | |
---|---|---|
Description | Monitors the network errors of a session. | |
Knowledge Article |
SummaryHelps to identify sessions that have networking errors/timeouts on end-user connections. This can result in a session being disconnected or having slow responsiveness. The name of the user, application, and client IP address are included in the alert details. This monitor is disabled by default because consecutive samples counterpart rule is enabled by default. | |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | XenApp Session Network Errors | |
Alert Message | Network errors of a session on {0} exceeded the threshold value. Total errors per second transferred: {1} Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CriticalThreshold | 20 |
WarningThreshold | 10 |
Priority | 1 |
Severity | -- defined with discovered object property -- |
Display Name | XenApp Session Network Traffic (Alert) | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | Monitors the network traffic of a session. | |||||||||
Knowledge Article |
SummaryHelps to identify sessions that host applications that require a large network bandwidth (animations, printing to a local printer, copying from a local USB drive). If bandwidth is limited and XenApp network throttling policies are not set accordingly, this can have a large impact on all other users working from the same remote office. The name of the user, application, and client IP address are included in the alert details. Alert is triggered only when network traffic rate is above threshold for specified number of consecutive samples (NumberOfSamples parameter). ConfigurationThe following configuration parameters are customizable:
Formula for ConsolidationInterval: ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1 Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples): IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990 | |||||||||
Target | XenApp | |||||||||
Enabled by default | No | |||||||||
Category | Alert | |||||||||
Generate Alert | True | |||||||||
Alert Name | XenApp Session Network Traffic | |||||||||
Alert Message | Network traffic (total bytes per second) of a session on {0} is above the threshold for multiple consecutive samples. Total bytes per second transferred: {1} Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
NumberOfSamples | 3 |
IntervalSeconds | 300 |
Threshold | 30000000 |
ConsolidationInterval | 660 |
Priority | 1 |
Severity | 1 |
Display Name | XenApp Session Network Traffic (non consecutive) (Alert) | |
---|---|---|
Description | Monitors the network traffic of a session. | |
Knowledge Article |
SummaryHelps to identify sessions that host applications that require a large network bandwidth (animations, printing to a local printer, copying from a local USB drive). If bandwidth is limited and XenApp network throttling policies are not set accordingly, this can have a large impact on all other users working from the same remote office. The name of the user, application, and client IP address are included in the alert details. This monitor is disabled by default because consecutive samples counterpart rule is enabled by default. | |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | XenApp Session Network Traffic | |
Alert Message | Network traffic (total bytes per second) of a session on {0} exceeded the threshold value. Total bytes per second transferred: {1} Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CriticalThreshold | 1000000 |
WarningThreshold | 500000 |
Priority | 1 |
Severity | -- defined with discovered object property -- |
Display Name | XenApp Session Page File Size (Alert) | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | Monitors the page file size of a session. | |||||||||
Knowledge Article |
SummaryAlert is triggered only when page file size is above threshold for specified number of consecutive samples (NumberOfSamples parameter). ConfigurationThe following configuration parameters are customizable:
Formula for ConsolidationInterval: ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1 Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples): IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990 | |||||||||
Target | XenApp | |||||||||
Enabled by default | No | |||||||||
Category | Alert | |||||||||
Generate Alert | True | |||||||||
Alert Name | XenApp Session Page File Size | |||||||||
Alert Message | Page file size of a session on {0} is above the threshold for multiple consecutive samples. Page file size: {1} MB Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
NumberOfSamples | 3 |
IntervalSeconds | 300 |
Threshold | 2000 |
ConsolidationInterval | 660 |
Priority | 1 |
Severity | 1 |
Display Name | XenApp Session Page File Size (non consecutive) (Alert) | |
---|---|---|
Description | Monitors the page file size of a session. | |
Knowledge Article |
SummaryHelps to identify sessions that host applications that are very likely leaking memory. The name of the user, application, and client IP address are included in the alert details. This monitor is disabled by default because consecutive samples counterpart rule is enabled by default. | |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | XenApp Session Page File Size | |
Alert Message | Page file size of a session on {0} exceeded the threshold value. Page file size: {1} MB Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CriticalThreshold | 2000 |
WarningThreshold | 1200 |
Priority | 1 |
Severity | -- defined with discovered object property -- |
Display Name | XenApp Session Thread Count (Alert) | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | Monitors the thread count of a session. | |||||||||
Knowledge Article |
SummaryHelps to identify sessions that host applications that are very likely leaking threads, which can potentially lead to unstable/slow session. The name of the user, application, and client IP address are included in the alert details. Alert is triggered only when thread count is above threshold for specified number of consecutive samples (NumberOfSamples parameter). ConfigurationThe following configuration parameters are customizable:
Formula for ConsolidationInterval: ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1 Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples): IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990 | |||||||||
Target | XenApp | |||||||||
Enabled by default | No | |||||||||
Category | Alert | |||||||||
Generate Alert | True | |||||||||
Alert Name | XenApp Session Thread Count | |||||||||
Alert Message | Thread count of a session on {0} is above the threshold for multiple consecutive samples. Thread count: {1} Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
NumberOfSamples | 3 |
IntervalSeconds | 300 |
Threshold | 3000 |
ConsolidationInterval | 660 |
Priority | 1 |
Severity | 1 |
Display Name | XenApp Session Thread Count (non consecutive) (Alert) | |
---|---|---|
Description | Monitors the thread count of a session. | |
Knowledge Article |
SummaryHelps to identify sessions that host applications that are very likely leaking threads, which can potentially lead to unstable/slow session. The name of the user, application, and client IP address are included in the alert details. This monitor is disabled by default because consecutive samples counterpart rule is enabled by default. | |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | XenApp Session Thread Count | |
Alert Message | Thread count of a session on {0} exceeded the threshold value. Thread count: {1} Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CriticalThreshold | 3000 |
WarningThreshold | 1000 |
Priority | 1 |
Severity | -- defined with discovered object property -- |
Display Name | XenApp Session Working Set Size (Alert) | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Description | Monitors the working set size of a session. | |||||||||
Knowledge Article |
SummaryHelps to identify sessions that host memory hungry applications. The name of the user, application, and client IP address are included in the alert details. Alert is triggered only when working set size is above threshold for specified number of consecutive samples (NumberOfSamples parameter). ConfigurationThe following configuration parameters are customizable:
Formula for ConsolidationInterval: ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1 Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples): IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990 | |||||||||
Target | XenApp | |||||||||
Enabled by default | Yes | |||||||||
Category | Alert | |||||||||
Generate Alert | True | |||||||||
Alert Name | XenApp Session Working Set Size | |||||||||
Alert Message | Working set size of a session on {0} is above the threshold for multiple consecutive samples. Working set size: {1} MB Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
NumberOfSamples | 3 |
IntervalSeconds | 300 |
Threshold | 2000 |
ConsolidationInterval | 660 |
Priority | 1 |
Severity | 1 |
Display Name | XenApp Session Working Set Size (non consecutive) (Alert) | |
---|---|---|
Description | Monitors the working set size of a session. | |
Knowledge Article |
SummaryHelps to identify sessions that host memory hungry applications. The name of the user, application, and client IP address are included in the alert details. This monitor is disabled by default because consecutive samples counterpart rule is enabled by default. | |
Target | XenApp | |
Enabled by default | No | |
Category | Alert | |
Generate Alert | True | |
Alert Name | XenApp Session Working Set Size | |
Alert Message | Working set size of a session on {0} exceeded the threshold value. Working set size: {1} MB Session info: Session name: {2} Session ID: {3} User: {4} Client info: {5} Client name: {6} Session type: {7} Session state: {8} Applications: {9} For more information about session see Alert Context section. |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CriticalThreshold | 2000 |
WarningThreshold | 1200 |
Priority | 1 |
Severity | -- defined with discovered object property -- |
Display Name | Publish Custom User Activity Event Log Messages DW | |
---|---|---|
Description | Collects events from custom event log, based on user name. Data is used in "XenApp logons and published application usage per user" report. Events are stored in Data Warehouse. "LogName" parameter must be set to enable collecting from specified event log. To exclude events with specific Event IDs, Event Levels, Event Sources or Event Users, override the "ExcludeEventIDs", "ExcludeEventLevels" , "ExcludeEventSources" or "ExcludeEventUsers" parameters. Parameters must be formatted as regex patterns. ExcludeEventIDs parameter override example: ^(1001)$|^(1002)$|^(1045)$ ExcludeEventLevels (1-Error, 2-Warning, 4-Information) parameter override example: ^(4)$ ExcludeEventUsers parameter override example: ^(DOMAIN\\Administrator)$|^(DOMAIN\\User)$ | |
Target | XenApp | |
Enabled by default | No | |
Category | EventCollection | |
Generate Alert | False |
Parameter | Default Value |
---|---|
ExcludeEventLevels | ^.{0,0}$ |
ExcludeEventIDs | ^.{0,0}$ |
ExcludeEventSources | ^.{0,0}$ |
ExcludeEventUsers | ^.{0,0}$ |
LogName |
Display Name | XenApp Application Event Log Collect - Information (Event) | |
---|---|---|
Description | Monitors the Application event log for XenApp specific information events. To exclude events with specific Event IDs or Event Sources, override the "ExcludeEventIDs" or "ExcludeEventSources" parameters. Parameters must be formatted as regex patterns. ExcludeEventIDs parameter override example: ^(1001)$|^(1002)$|^(1045)$ | |
Knowledge Article |
SummaryForwards Citrix-related Application Event Log issues to MS Operations Manager. | |
Target | XenApp | |
Enabled by default | No | |
Category | EventCollection | |
Generate Alert | False |
Parameter | Default Value |
---|---|
ExcludeEventIDs | ^.{0,0}$ |
ExcludeEventSources | ^.{0,0}$ |
Display Name | XenApp Application Event Log Collect - Warnings and Errors (Event) | |
---|---|---|
Description | Monitors the Application event log for XenApp specific warning and error events. To exclude events with specific Event IDs or Event Sources, override the "ExcludeEventIDs" or "ExcludeEventSources" parameters. Parameters must be formatted as regex patterns. ExcludeEventIDs parameter override example: ^(1001)$|^(1002)$|^(1045)$ | |
Knowledge Article |
SummaryForwards Citrix-related Application Event Log issues to MS Operations Manager. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | EventCollection | |
Generate Alert | False |
Parameter | Default Value |
---|---|
ExcludeEventIDs | ^.{0,0}$ |
ExcludeEventSources | ^.{0,0}$ |
Display Name | XenApp Security Event Log Collect - Information (Event) | |
---|---|---|
Description | Monitors the Security event log for XenApp specific warning and error events. To exclude events with specific Event IDs or Event Sources, override the "ExcludeEventIDs" or "ExcludeEventSources" parameters. Parameters must be formatted as regex patterns. ExcludeEventIDs parameter override example: ^(1001)$|^(1002)$|^(1045)$ | |
Knowledge Article |
SummaryForwards Citrix-related Security Event Log issues to MS Operations Manager. | |
Target | XenApp | |
Enabled by default | No | |
Category | EventCollection | |
Generate Alert | False |
Parameter | Default Value |
---|---|
ExcludeEventIDs | ^.{0,0}$ |
ExcludeEventSources | ^.{0,0}$ |
Display Name | XenApp Security Event Log Collect - Warnings and Errors (Event) | |
---|---|---|
Description | Monitors the Security event log for XenApp specific warning and error events. To exclude events with specific Event IDs or Event Sources, override the "ExcludeEventIDs" or "ExcludeEventSources" parameters. Parameters must be formatted as regex patterns. ExcludeEventIDs parameter override example: ^(1001)$|^(1002)$|^(1045)$ | |
Knowledge Article |
SummaryForwards Citrix-related Security Event Log issues to MS Operations Manager. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | EventCollection | |
Generate Alert | False |
Parameter | Default Value |
---|---|
ExcludeEventIDs | ^.{0,0}$ |
ExcludeEventSources | ^.{0,0}$ |
Display Name | XenApp System Event Log Collect - Information (Event) | |
---|---|---|
Description | Monitors the System event log for XenApp specific information events. To exclude events with specific Event IDs or Event Sources, override the "ExcludeEventIDs" or "ExcludeEventSources" parameters. Parameters must be formatted as regex patterns. ExcludeEventIDs parameter override example: ^(1001)$|^(1002)$|^(1045)$ | |
Knowledge Article |
SummaryForwards Citrix-related System Event Log issues to MS Operations Manager. | |
Target | XenApp | |
Enabled by default | No | |
Category | EventCollection | |
Generate Alert | False |
Parameter | Default Value |
---|---|
ExcludeEventIDs | ^.{0,0}$ |
ExcludeEventSources | ^.{0,0}$ |
Display Name | XenApp System Event Log Collect - Warnings and Errors (Event) | |
---|---|---|
Description | Monitors the System event log for XenApp specific warning and error events. To exclude events with specific Event IDs or Event Sources, override the "ExcludeEventIDs" or "ExcludeEventSources" parameters. Parameters must be formatted as regex patterns. ExcludeEventIDs parameter override example: ^(1001)$|^(1002)$|^(1045)$ | |
Knowledge Article |
SummaryForwards Citrix-related System Event Log issues to MS Operations Manager. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | EventCollection | |
Generate Alert | False |
Parameter | Default Value |
---|---|
ExcludeEventIDs | ^.{0,0}$ |
ExcludeEventSources | ^.{0,0}$ |
Display Name | Active XenApp Sessions (Performance DB DW) | |
---|---|---|
Description | Collects the number of active sessions. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Active Sessions (Count) |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | All XenApp Sessions (Performance DB DW) | |
---|---|---|
Description | Collects the number of all sessions. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | All Sessions (Count) |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | Custom File Count of User Profile (Performance DB DW) | |
---|---|---|
Description | Collects the custom file count of a user profile. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Custom File Count |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | Disconnected XenApp Sessions (Performance DB DW) | |
---|---|---|
Description | Collects the number of disconnected sessions. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Disconnected Sessions (Count) |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | Down XenApp Sessions (Performance DB DW) | |
---|---|---|
Description | Collects the number of down sessions. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Down Sessions (Count) |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | Executable File Count of User Profile (Performance DB DW) | |
---|---|---|
Description | Collects the executable file count of a user profile. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Executable File Count |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | Media File Count of User Profile (Performance DB DW) | |
---|---|---|
Description | Collects the media file count of a user profile. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Media File Count |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | Publish XenApp Process Details DW | |||||||
---|---|---|---|---|---|---|---|---|
Description | Collects top process information on a XenApp server. Data is stored in Data Warehouse. To select the type of process collection, override the CollectionType parameter with: ALL - all processes will be collected LIST process_name_1.exe process_name_2.exe ... - specified processes will be collected TOP CPU MEM N - top N processes with highest CPU and/or Memory (working set) will be collected. CPU and MEM parameters are optional. N represents the number of top processes. Default parameter value is "TOP CPU 10". | |||||||
Knowledge Article |
SummaryCollects top process information on XenApp server. Data is stored in Data Warehouse. To select the type of process collection, override the CollectionType parameter with:
Default parameter value is TOP CPU 10. | |||||||
Target | XenApp | |||||||
Enabled by default | No (disabled by override) | |||||||
Category | PerformanceCollection | |||||||
Generate Alert | False |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
CollectionType | TOP CPU 10 |
Display Name | Publish XenApp User Logon Details DW | |
---|---|---|
Description | Collects all logon information on XenApp server. Data is stored in Data Warehouse. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False |
Parameter | Default Value |
---|---|
IntervalSeconds | 120 |
Display Name | Publish XenApp User Session Details DW | |||||
---|---|---|---|---|---|---|
Description | Collects all user session information per published application on XenApp server. Data is stored in Data Warehouse. | |||||
Knowledge Article |
SummaryThis rule collects all user session information per published application on XenApp server. Data is stored in Data Warehouse and is used for reports. To change session data collection interval, override the IntervalSeconds parameter. Value is entered in seconds. Default IntervalSeconds parameter value is 300 (5 minutes). It is essential that when IntervalSeconds parameter is updated, ComTradeXAMP.SessionCollectingInterval table in OperationsManagerDW database is also updated shortly before or afterwards. New record has to be added with the following values:
| |||||
Target | XenApp | |||||
Enabled by default | No (disabled by override) | |||||
Category | PerformanceCollection | |||||
Generate Alert | False |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | Total File Count of All User Profiles (Performance DB DW) | |
---|---|---|
Description | Collects the total file count of all user profiles. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Sum Total File (Count) |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | Total File Count of User Profile (Performance DB DW) | |
---|---|---|
Description | Collects the total file count of a user profile. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Total File Count |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | Total File Size of All User Profiles (Performance DB DW) | |
---|---|---|
Description | Collects the total file size of all user profiles. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Sum Total File Size (MB) |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | Total File Size of User Profile (Performance DB DW) | |
---|---|---|
Description | Collects the total file size of a user profile. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Total File Size (MB) |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Logons (Performance DW) (OBSOLETE) | |
---|---|---|
Description | Stores all user logons to the MS Operations Manager Data Warehouse. OBSOLETE NOTE: This rule is replaced by "Publish XenApp User Logon Details DW" rule in Citrix Management Pack for XenApp 6.x Reports. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False |
Parameter | Default Value |
---|---|
ServerName | -- defined with discovered object property -- |
SyncTime | |
IntervalSeconds | 120 |
Display Name | XenApp Server Application Enumerations (Performance DB) | |
---|---|---|
Description | Collects the number of Application Enumerations/sec on XenApp Server. | |
Knowledge Article |
SummaryThis rule collects the number of Application Enumerations per second on XenApp Server and stores data to Operations database. Application Enumerations is the number of non-XML-based enumerations (requests for application lists). | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Object Name | Citrix MetaFrame Presentation Server | |
Counter Name | Application Enumerations/sec |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Server Application Resolution Time (Performance DB) | |
---|---|---|
Description | Collects the Application Resolution Time (in ms) on XenApp Server. | |
Knowledge Article |
SummaryThis rule collects the Application Resolution Time in milliseconds on XenApp Server and stores data to Operations database. Application Resolution Time is the time required to resolve the Least-Loaded Server during an application launch. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Object Name | Citrix MetaFrame Presentation Server | |
Counter Name | Application Resolution Time (ms) |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Server Average ICA Latency (Performance DW) | |
---|---|---|
Description | Collects average latency of all active ICA sessions on XenApp server and stores data to Data Warehouse. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | AvgICALatency |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Server CPU Usage (Performance DW) | |
---|---|---|
Description | Collects the XenApp server CPU usage (in %) and stores data to Data Warehouse. | |
Knowledge Article |
SummaryThis rule collects the CPU usage (in %) on XenApp server and stores data to Data Warehouse. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | CPU Usage |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Server Disk Load (Performance DW) | |
---|---|---|
Description | Collects the XenApp server disk read/write time (in %) and stores data to Data Warehouse. | |
Knowledge Article |
SummaryThis rule collects the disk read/write time (in %) on XenApp server and stores data to Data Warehouse. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Disk Load |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Server Disk Used Space (Performance DW) | |
---|---|---|
Description | Collects the XenApp server disk used space (in %) and stores data to Data Warehouse. | |
Knowledge Article |
SummaryThis rule collects disk used space (in %) on XenApp server and stores data to Data Warehouse. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Disk Space Usage |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Server Filtered Application Enumerations (Performance DB) | |
---|---|---|
Description | Collects the number of Filtered Application Enumerations/sec on XenApp Server. | |
Knowledge Article |
SummaryThis rule collects the number of Filtered Application Enumerations per second on XenApp Server and stores data to Operations database. Filtered Application Enumerations is the number of Web Interface/StoreFront application enumerations (and logons) per second handled by specific XML broker. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Object Name | Citrix MetaFrame Presentation Server | |
Counter Name | Filtered Application Enumerations/sec |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Server IO Data Operations per Sec (Performance DW) | |
---|---|---|
Description | Collects the total IO Data Operations per Second for all processes and stores data to Data Warehouse. IO Data Operations per sec. is the rate at which the process is issuing read and write I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os. | |
Knowledge Article |
SummaryCollects the total IO Data Operations per Second for all processes and stores data to Data Warehouse. IO Data Operations per sec. is the rate at which the process is issuing read and write I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | IO Data Operations |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Server Load (Performance DB DW) | |
---|---|---|
Description | Collects the XenApp server load (in %). | |
Knowledge Article |
SummaryThis rule collects the load of the XenApp server (in %). | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Server Load (%) |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Server Memory Usage (Performance DW) | |
---|---|---|
Description | Collects the XenApp server memory usage (in %) and stores data to Data Warehouse. | |
Knowledge Article |
SummaryThis rule collects the memory usage (in %) on XenApp server and stores data to Data Warehouse. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Memory Usage |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Server Network Usage (Performance DW) | |
---|---|---|
Description | Collects the average network usage through all network interfaces (in %) on XenApp server and stores data to Data Warehouse. | |
Knowledge Article |
SummaryThis rule collects the average network usage through all network interfaces (in %) on XenApp server and stores data to Data Warehouse. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Network Usage |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Server Number of Busy XML Threads (Performance DB) | |
---|---|---|
Description | Collects the number of busy XML threads on XenApp Server. | |
Knowledge Article |
SummaryThis rule collects the number of busy XML threads on XenApp Server and stores data to Operations database. Number of busy XML threads is the number of XML requests that are currently being processed. The maximum number of requests that the XML service can process at any one time is 16. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Object Name | Citrix MetaFrame Presentation Server | |
Counter Name | Number of busy XML threads |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Server Zone Elections Triggered (Performance DB) | |
---|---|---|
Description | Collects the number of triggered zone elections for each monitoring interval. | |
Knowledge Article |
SummaryThis rule collects the number of triggered zone elections by XenApp server for each monitoring interval. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Object Name | Citrix MetaFrame Presentation Server | |
Counter Name | Zone Elections Triggered |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Session CPU Utilization (Performance DB DW) | |
---|---|---|
Description | Collects the CPU utilization of a session. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | CPU Usage |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Session Handle Count (Performance DB DW) | |
---|---|---|
Description | Collects the handle count of a session. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Handle Count |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Session Latency - Average (Performance DB DW) | |
---|---|---|
Description | Collects the average latency (in milliseconds) of a session. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Latency Session Average (ms) |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Session Latency - Deviation (Performance DB DW) | |
---|---|---|
Description | Collects the latency deviation (in milliseconds) of a session. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Latency Session Deviation (ms) |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Session Latency - Last Recorded (Performance DB DW) | |
---|---|---|
Description | Collects the last recorded latency (in milliseconds) of a session. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Latency Last Recorded (ms) |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Session Network Errors (Performance DB DW) | |
---|---|---|
Description | Collects the network errors of a session. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Network Errors |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Session Network Traffic (Performance DB DW) | |
---|---|---|
Description | Collects the network traffic of a session. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Network Traffic |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Session Page File Size (Performance DB DW) | |
---|---|---|
Description | Collects the page file size of a session. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Page File Size (MB) |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Session Thread Count (Performance DB DW) | |
---|---|---|
Description | Collects the thread count of a session. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Thread Count |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Session Working Set Size (Performance DB DW) | |
---|---|---|
Description | Collects the working set size of a session. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Working Set Size (MB) |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp User Session - Active Sessions (Performance DW) | |
---|---|---|
Description | Collects active user sessions per published application on XenApp server. Data is stored in Data Warehouse. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Active Sessions |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp User Session - Application Instances (Performance DW) | |
---|---|---|
Description | Collects total running application instances per published application on XenApp server. Data is stored in Data Warehouse. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Application Instances |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp User Session - Inactive Sessions (Performance DW) | |
---|---|---|
Description | Collects inactive user sessions per published application on XenApp server. Data is stored in Data Warehouse. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Inactive Sessions |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp User Session - Total Sessions (Performance DW) | |
---|---|---|
Description | Collects total user sessions per published application on XenApp server. Data is stored in Data Warehouse. | |
Target | XenApp | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Total Sessions |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp User Session Details DW (Performance DW) (OBSOLETE) | |
---|---|---|
Description | Collects all user session information per published application on XenApp server. Data is stored in Data Warehouse. OBSOLETE NOTE: This rule is replaced by "Publish XenApp User Session Details DW" rule in Citrix Management Pack for XenApp 6.x Reports. | |
Target | XenApp | |
Enabled by default | No | |
Category | PerformanceCollection | |
Generate Alert | False |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Application Load (Performance DB DW) | |
---|---|---|
Description | Collects the number of running instances of a published application. | |
Target | Zone Data Collector | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Count |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Zone Off-line Servers (Performance DB DW) | |
---|---|---|
Description | Collects the number of off-line servers in a XenApp zone. | |
Target | Zone Data Collector | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Off-line Servers (Count) |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Display Name | XenApp Zone Off-line Servers Percentage (Performance DB DW) | |
---|---|---|
Description | Collects the percentage of off-line servers in a XenApp zone. | |
Target | Zone Data Collector | |
Enabled by default | Yes | |
Category | PerformanceCollection | |
Generate Alert | False | |
Counter Name | Off-line Servers Percentage |
Parameter | Default Value |
---|---|
IntervalSeconds | 300 |
Target | Category | Display Name | Roll-up Algorithm |
---|---|---|---|
XenApp Computer Role | |||
Custom | |||
Installation | WorstOf | ||
XenApp Availability | |||
AvailabilityHealth | |||
XenApp Server Availability | WorstOf | ||
Zone Data Collector | |||
Custom | |||
ZDC Zone | WorstOf | ||
Citrix Management | |||
Custom | |||
XenApp Farms Dependency Monitor | WorstOf | ||
AvailabilityHealth | |||
XenApp Farms Availability Dependency Monitor | WorstOf | ||
Application | |||
AvailabilityHealth | |||
XenApp Application Availability | BestOf | ||
Application Folder | |||
Custom | |||
XenApp Application Performance Dependency Monitor | WorstOf | ||
XenApp Application Folder Availability Dependency Monitor | WorstOf | ||
XenApp Application Folder Performance Dependency Monitor | WorstOf | ||
XenApp Application Availability Dependency Monitor | WorstOf | ||
XenApp | |||
Custom | |||
XenApp Availability Dependency Monitor | WorstOf | ||
Service Group Dependency Monitor | WorstOf | ||
TCP Probe Dependency Monitor | WorstOf | ||
Farm | |||
Custom | |||
XenApp Folder Dependency Monitor | WorstOf | ||
Zone Group Dependency Monitor | WorstOf | ||
XenApp Farms | |||
AvailabilityHealth | |||
Farm Availability Dependency Monitor | WorstOf | ||
Custom | |||
Farm Dependency Monitor | WorstOf | ||
Services Group | |||
Custom | |||
Terminal Server Services Dependency Monitor | WorstOf | ||
XenApp Services Dependency Monitor | WorstOf | ||
XenApp Folder | |||
Custom | |||
XenApp Dependency Monitor | WorstOf | ||
XenApp Folder Dependency Monitor | WorstOf | ||
Zone Data Collector Dependency Monitor | WorstOf | ||
Zone | |||
Custom | |||
XenApp Dependency Monitor | WorstOf | ||
Zone Data Collector Dependency Monitor | WorstOf | ||
Zone Group | |||
Custom | |||
XenApp Zone Dependency Monitor | WorstOf |
Target | Display Name | Description | Parameters | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
XenApp Computer Role | Check Requirements and Configuration for Citrix MPXA Agent | Checks if a Citrix system meets the requirements for Citrix Management Pack Agent for XenApp 6.x . |
--- | ||||||||
XenApp Computer Role | Collect Support Information for Citrix MPXA Agent | Collects support information for XenApp Management Pack Agent. |
--- | ||||||||
XenApp Computer Role | Install Citrix MPXA Agent | Installs Citrix Management Pack Agent for XenApp 6.x on the Citrix system. Parameters: - AgentInstallationSource: Agent installation and configuration source is specified as either with the management server name where XenApp MP was installed or with the UNC path where XenApp MP Agent installation and configuration files exist. If not specified, the task tries to identify the management server automatically. - AgentInstallationDestination: Specify the agent installation destination folder optionally. - UpgradeAgent: If true, then, existing agent is uninstalled initially and then the new one is installed. Before the agent is upgraded, put the managed node in the maintenance during the installation. |
| ||||||||
XenApp Computer Role | Restart Citrix MPXA Agent Service | Restarts Citrix Management Pack Agent for XenApp 6.x on the Citrix system. |
--- | ||||||||
XenApp Computer Role | Uninstall Citrix MPXA Agent | Uninstalls Citrix Management Pack Agent for XenApp 6.x from the Citrix system. |
--- | ||||||||
XenApp Computer Role | Update Configuration on Citrix MPXA Agent | Updates Configuration on Citrix Management Pack Agent for XenApp 6.x. Parameters: - AgentInstallationSource: Agent installation and configuration source is specified as either with the management server name where XenApp MP was installed or with the UNC path where XenApp MP Agent installation and configuration files exist. If not specified, the task tries to identify the management server automatically. |
| ||||||||
Citrix XenApp MP Agent Service | Check Requirements and Configuration for Citrix MPXA Agent | Checks if a Citrix system meets the requirements for Citrix Management Pack Agent for XenApp 6.x . |
--- | ||||||||
Citrix XenApp MP Agent Service | Update Configuration on Citrix MPXA Agent | Updates Configuration on Citrix Management Pack Agent for XenApp 6.x. Parameters: - AgentInstallationSource: Agent installation and configuration source is specified as either with the management server name where XenApp MP was installed or with the UNC path where XenApp MP Agent installation and configuration files exist. If not specified, the task tries to identify the management server automatically. |
| ||||||||
XenApp | Check Requirements and Configuration for Citrix MPXA Agent | Checks if a Citrix system meets the requirements for Citrix Management Pack Agent for XenApp 6.x |
--- | ||||||||
XenApp | Collect Support Information for Citrix MPXA Agent | Collects support information for XenApp Management Pack Agent. |
--- | ||||||||
XenApp | Restart Citrix MPXA Agent Service | Restarts Citrix Management Pack Agent for XenApp 6.x on the Citrix system. |
--- | ||||||||
XenApp | Update Configuration on Citrix MPXA Agent | Updates Configuration on Citrix Management Pack Agent for XenApp 6.x. Parameters: - AgentInstallationSource: Agent installation and configuration source is specified as either with the management server name where XenApp MP was installed or with the UNC path where XenApp MP Agent installation and configuration files exist. If not specified, the task tries to identify the management server automatically. |
| ||||||||
XenApp | Display All Sessions | Displays detailed session information on a server. |
--- | ||||||||
XenApp | Display User Logons | Displays detailed logon information of logons performed by a specified user. Parameters: - UserName: The username for which the logon info needs to be displayed |
| ||||||||
XenApp | Display Recent User Logons | Displays detailed logon information of the recently logged on users. Parameters: - LastMinutes: The time interval in minutes, according to which the logons should be checked |
| ||||||||
XenApp | Display User Profiles | Displays detailed profile information on a server. |
--- |
Folder | Display Name | Description | Target | Category |
---|---|---|---|---|
Citrix Library | Citrix Management Topology | This view displays topology for all Citrix Management Packs. |
Citrix Management | Topology |
Citrix Library | XenApp 6.x Computers | This view displays all computers with Citrix XenApp installed including info whether MPXA agent is installed on the node and MPXA agent version. It shows also MPXA agent service health state and all alerts related to MPXA agent. |
XenApp Computer Role | HealthState |
Citrix XenApp 6.x | XenApp Alerts | This view displays all active and closed alerts. |
XenApp Farms | Alerts |
Citrix XenApp 6.x | XenApp Events | This view displays all events forwarded from the Windows Event Log related to Citrix XenApp. |
XenApp | Events |
Citrix XenApp 6.x | XenApp Farm State | This view displays a health state for all farms. |
Farm | State |
Citrix XenApp 6.x | XenApp State | This view displays a health state for all XenApp servers. |
XenApp | State |
Citrix XenApp 6.x | XenApp Topology | This view displays the XenApp Topology. |
XenApp Farms | Topology |
Citrix XenApp 6.x | XenApp Zone Data Collector State | This view displays a health state for all XenApp zone data collectors. |
Zone Data Collector | State |
Citrix XenApp 6.x | XenApp Zone State | This view displays a health state for all zones. |
Zone | State |
Citrix XenApp 6.x->XenApp Applications | XenApp Application Alerts | This view displays active and closed application alerts. |
Application | Alerts |
Citrix XenApp 6.x->XenApp Applications | XenApp Application State | This view displays a health state for all applications. |
Application | State |
Citrix XenApp 6.x->XenApp Applications | XenApp Disabled Applications | This view displays all disabled published applications. |
Application | State |
Citrix XenApp 6.x->XenApp Performance | XenApp Server Load | This view displays a graph showing XA server load in %. |
XenApp | Performance |
Citrix XenApp 6.x->XenApp Performance | XenApp Server Performance | This view displays a graph showing the Citrix MetaFrame Presentation Server performance counters. |
XenApp | Performance |
Citrix XenApp 6.x->XenApp Performance | XenApp Session Summary | This view displays a graph showing the number of all/active/disconnected/down sessions. |
XenApp | Performance |
Citrix XenApp 6.x->XenApp Performance | XenApp Zone Off-line Servers | This view displays a graph showing the number of all off-line servers in a XenApp zone. |
Zone Data Collector | Performance |
Citrix XenApp 6.x->XenApp Services | Terminal Server Service Performance | This view displays a graph showing performance counters (CPU utilization, memory, ...) for each Terminal Server service. |
Terminal Server Service | Performance |
Citrix XenApp 6.x->XenApp Services | Terminal Server Service State | This view displays a health state for all Terminal Server services. |
Terminal Server Service | State |
Citrix XenApp 6.x->XenApp Services | XenApp Service Performance | This view displays a graph showing performance counters (CPU utilization, memory, ...) for each XenApp service. |
XenApp Service | Performance |
Citrix XenApp 6.x->XenApp Services | XenApp Service State | This view displays a health state for all XenApp services. |
XenApp Service | State |
Citrix XenApp 6.x->XenApp Sessions | XenApp Session Alerts | This view displays active and closed session alerts. |
XenApp | Alerts |
Citrix XenApp 6.x->XenApp Sessions | XenApp Sessions | This view displays a graph showing performance counters (CPU utilization, memory, latency, network traffic, ...) for each active session. |
XenApp | Performance |
Citrix XenApp 6.x->XenApp User Logon Process | XenApp User Logon Process Alerts | This view displays active and closed user logon process alerts. |
XenApp | Alerts |
Citrix XenApp 6.x->XenApp User Profile | XenApp User Profile | This view displays a graph showing the number of custom/executable/media/total files in user profile and total profile size. |
XenApp | Performance |
Citrix XenApp 6.x->XenApp User Profile | XenApp User Profile Alerts | This view displays all active and closed alerts for each separate user profile. |
XenApp | Alerts |
Citrix XenApp 6.x->XenApp User Profile | XenApp User Profile Summary | This view displays a graph showing the number of files in all user profiles and cumulative size of all user profiles. |
XenApp | Performance |
Citrix XenApp 6.x->XenApp User Profile | XenApp User Profiles Alerts | This view displays all active and closed alerts for all user profiles. |
XenApp | Alerts |
Target | Name | Description |
---|---|---|
Daily Logons for Farm(s) | This report shows the number of total user logons and the number of unique user logons per day for selected XenApp Farm(s). The number of unique user logons is the number of distinct users that logged on to XenApp. Logon data is shown also for each server belonging to the farm. Report depends on the following data collecting rule(s): - Publish XenApp User Logon Details DW | |
Daily Logons for Server(s) | This report shows the number of total user logons and the number of unique user logons per day for selected XenApp Server(s). The number of unique user logons is the number of distinct users that logged on to XenApp. Report depends on the following data collecting rule(s): - Publish XenApp User Logon Details DW | |
Logon time distribution for Farm(s) | This report shows a breakdown of user logon times into 5-second slots for selected XenApp Farm(s). Logon time distribution is shown also for each server belonging to the farm. Report depends on the following data collecting rule(s): - Publish XenApp User Logon Details DW | |
Logon time distribution for Server(s) | This report shows a breakdown of user logon times into 5-second slots for selected XenApp Server(s). Report depends on the following data collecting rule(s): - Publish XenApp User Logon Details DW | |
User Growth Over Time for Farm(s) | This report shows how many unique (distinct) users are logging into selected XenApp Farm(s) over time. The first chart represents number of unique (distinct) user over time. Number for each day represents number of unique users using farm from the start of reporting range to that day. The second chart shows the users growth (increment) per day, i.e. number of new unique (distinct) users that logged on specific day. Report depends on the following data collecting rule(s): - Publish XenApp User Logon Details DW | |
User logons | This report shows the average logon duration for each individual user (number of logons, min/max). The Details table shows logon details (Logon time, Username, Client name, XA Server, Session ID, Login type, complete logon duration, and duration for all 5 logon phases). Report depends on the following data collecting rule(s): - Publish XenApp User Logon Details DW | |
Application | User sessions per published application | This report shows the number of user sessions (total, active, inactive) and the running application instances for selected applications. The Details table shows information per each XenApp server. Report depends on the following data collecting rule(s): - XenApp User Session - Active Sessions (Performance DW) - XenApp User Session - Application Instances (Performance DW) - XenApp User Session - Inactive Sessions (Performance DW) - XenApp User Session - Total Sessions (Performance DW) |
Application | XenApp application availability | This report shows the availability of application and the availability of XenApp servers that publish individual application. The Details table shows information for each XenApp server. |
Application | XenApp published application overview | This report shows user sessions, performance and availability overview for XenApp servers that publish individual applications. Each sub-report can be drilled-down to a detailed report. Report depends on the following data collecting rule(s): - XenApp Server CPU Usage (Performance DW) - XenApp Server Disk Used Space (Performance DW) - XenApp Server Disk Load (Performance DW) - XenApp Server Load (Performance DB DW) - XenApp Server Memory Usage (Performance DW) - XenApp Server Network Usage (Performance DW) - XenApp Server Average ICA Latency (Performance DW) - XenApp User Session - Active Sessions (Performance DW) - XenApp User Session - Application Instances (Performance DW) - XenApp User Session - Inactive Sessions (Performance DW) - XenApp User Session - Total Sessions (Performance DW) |
Application | XenApp server performance (by published application) | This report shows server performance (CPU, memory, disk, network, server load, IOPS and average ICA latency) for XenApp servers that publish individual applications. The Details table shows information for each XenApp server. Report depends on the following data collecting rule(s): - XenApp Server Average ICA Latency (Performance DW) - XenApp Server CPU Usage (Performance DW) - XenApp Server Disk Used Space (Performance DW) - XenApp Server Disk Load (Performance DW) - XenApp Server IO Data Operations per Sec (Performance DW) - XenApp Server Load (Performance DB DW) - XenApp Server Memory Usage (Performance DW) - XenApp Server Network Usage (Performance DW) Description of metrics: CPU usage (%) - The sum of “Percent Processor Time” of all CPU cores. MEM usage (%) - Percent of physical memory used by processes on a system. Disk load (%) - Percent of elapsed time that hard drive was busy servicing read or write requests. Used space (%) - Percent of total used space on all logical disks on a system. Network load (%) - Percent of network usage (current network traffic / network interface bandwidth). The value is an average of all network interface instances on a system. Server load (%) - Load on a server, defined by Citrix load evaluator. Values are in percent. If Server load reaches 100%, XenApp server no longer allows new connections. Total IO Data Operations per sec. (IOPS) - The rate at which all processes on a system are issuing read and write I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os. Average ICA latency (ms) - Average ICA latency is the average latency of all active ICA sessions on a server, measured in milliseconds. |
Application | XenApp user activity (on published application) | This report shows user activity (application usage, session info) on individual published applications. Report depends on the following data collecting rule(s): - Publish XenApp User Session Details DW (disabled by default, override 'Enabled' parameter) Report requires XenApp MP Agent installed on Zone Data Collectors. |
XenApp | Number of active sessions on server (Trending) | This report is predicting the future average number of active sessions based on performance history. Report depends on the following data collecting rule(s): - Active XenApp Sessions (Performance DB DW) |
XenApp | Number of all sessions on server (Trending) | This report is predicting the future average number of all sessions based on performance history. Report depends on the following data collecting rule(s): - All XenApp Sessions (Performance DB DW) |
XenApp | Number of disconnected sessions on server (Trending) | This report is predicting the future average number of disconnected sessions based on performance history. Report depends on the following data collecting rule(s): - Disconnected XenApp Sessions (Performance DB DW) |
XenApp | Number of down sessions on server (Trending) | This report is predicting the future average number of down sessions based on performance history. Report depends on the following data collecting rule(s): - Down XenApp Sessions (Performance DB DW) |
XenApp | Number of user files on server (Trending) | This report is predicting the future average total file count of all user profiles based on performance history. Report depends on the following data collecting rule(s): - Total File Count of All User Profiles (Performance DB DW) (disabled by default, override 'Enabled' parameter) |
XenApp | Server load (%) (Trending) | This report is predicting the future average server load based on performance history. Report depends on the following data collecting rule(s): - XenApp Server Load (Performance DB DW) |
XenApp | Server load (Top N) | This report shows server load (Top N). Report depends on the following data collecting rule(s): - XenApp Server Load (Performance DB DW) |
XenApp | Server logons | This report shows the number of logons, min/max and the average logon duration for each individual XenApp server. The Details table shows logon details (Logon time, Username, Client name, XA Server, Session ID, Login type, complete logon duration, and duration for all 5 logon phases). Report depends on the following data collecting rule(s): - Publish XenApp User Logon Details DW |
XenApp | Servers with top active sessions (Top N) | This report shows servers with top active sessions (Top N). Report depends on the following data collecting rule(s): - Active XenApp Sessions (Performance DB DW) |
XenApp | Servers with top disconnected sessions (Top N) | This report shows servers with top disconnected sessions (Top N). Report depends on the following data collecting rule(s): - Disconnected XenApp Sessions (Performance DB DW) |
XenApp | Servers with top down sessions (Top N) | This report shows servers with top down sessions (Top N). Report depends on the following data collecting rule(s): - Down XenApp Sessions (Performance DB DW) |
XenApp | Servers with top profile file count (Top N) | This report shows servers with top profile file count (Top N). Report depends on the following data collecting rule(s): - Total File Count of All User Profiles (Performance DB DW) (disabled by default, override 'Enabled' parameter) |
XenApp | Servers with top profiles size (Top N) | This report shows servers with top profiles size (Top N). Report depends on the following data collecting rule(s): - Total File Size of All User Profiles (Performance DB DW) (disabled by default, override 'Enabled' parameter) |
XenApp | Servers with top sessions (Top N) | This report shows servers with top sessions (Top N). Report depends on the following data collecting rule(s): - All XenApp Sessions (Performance DB DW) |
XenApp | Size of all profiles on server (Trending) | This report is predicting the future average total file size of all user profiles based on performance history. Report depends on the following data collecting rule(s): - Total File Size of All User Profiles (Performance DB DW) (disabled by default, override 'Enabled' parameter) |
XenApp | XenApp logons and published application usage per user | This report shows user logons and published applications usage for individual users. Report depends on the following data collecting rule(s): - Publish XenApp User Session Details DW (disabled by default, override 'Enabled' parameter) - Publish XenApp User Logon Details DW Report requires XenApp MP Agent installed on Zone Data Collectors. To add custom user based events from event log, enable "Publish Custom User Activity Event Log Messages DW" rule and override "LogName" parameter (and optional exclude parameters). |
XenApp | XenApp server availability | This report shows the availability of individual XenApp servers. The Details table shows information for each XenApp server. |
XenApp | XenApp server performance | This report shows server performance (CPU, memory, disk, network, server load, IOPS and average ICA latency) for individual XenApp servers. The Details table shows information for each XenApp server. Report depends on the following data collecting rule(s): - XenApp Server Average ICA Latency (Performance DW) - XenApp Server CPU Usage (Performance DW) - XenApp Server Disk Used Space (Performance DW) - XenApp Server Disk Load (Performance DW) - XenApp Server IO Data Operations per Sec (Performance DW) - XenApp Server Load (Performance DB DW) - XenApp Server Memory Usage (Performance DW) - XenApp Server Network Usage (Performance DW) Description of metrics: CPU usage (%) - The sum of “Percent Processor Time” of all CPU cores. MEM usage (%) - Percent of physical memory used by processes on a system. Disk load (%) - Percent of elapsed time that hard drive was busy servicing read or write requests. Used space (%) - Percent of total used space on all logical disks on a system. Network load (%) - Percent of network usage (current network traffic / network interface bandwidth). The value is an average of all network interface instances on a system. Server load (%) - Load on a server, defined by Citrix load evaluator. Values are in percent. If Server load reaches 100%, XenApp server no longer allows new connections. Total IO Data Operations per sec. (IOPS) - The rate at which all processes on a system are issuing read and write I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os. Average ICA latency (ms) - Average ICA latency is the average latency of all active ICA sessions on a server, measured in milliseconds. |
XenApp | XenApp server performance (Top N) | This report shows top N XenApp servers with highest CPU or memory usage. Report depends on the following data collecting rule(s): - XenApp Server CPU Usage (Performance DW) - XenApp Server Memory Usage (Performance DW) |
XenApp | XenApp server process performance | This report shows performance metrics (CPU Usage, Working Set Size, Page File Size, IO Data Operations and Page Faults) for processes that are running on XenApp servers. Report depends on the following data collecting rule(s): - Publish XenApp Process Details DW (disabled by default, override 'Enabled' parameter) |
XenApp | XenApp user activity (on server) | This report shows user activity (application usage, session info) on individual servers. Report depends on the following data collecting rule(s): - Publish XenApp User Session Details DW (disabled by default, override 'Enabled' parameter) Report requires XenApp MP Agent installed on Zone Data Collectors. |
Zone | Number of offline servers in zone (Trending) | This report is predicting the future average number of offline servers in a zone based on performance history. Report depends on the following data collecting rule(s): - XenApp Zone Off-line Servers (Performance DB DW) |
Zone | Percentage of offline servers in zone (Trending) | This report is predicting the future average percentage of offline servers in a zone based on performance history. Report depends on the following data collecting rule(s): - XenApp Zone Off-line Servers Percentage (Performance DB DW) |
Zone | Zones with top offline server percentage (Top N) | This report shows zones with top offline server percentage (Top N). Report depends on the following data collecting rule(s): - XenApp Zone Off-line Servers Percentage (Performance DB DW) |
Zone | Zones with top offline servers (Top N) | This report shows zones with top offline servers (Top N). Report depends on the following data collecting rule(s): - XenApp Zone Off-line Servers (Performance DB DW) |
Application | Application use accounting | This report shows cumulative time the individual users have spent using specified published applications. Report depends on the following data collecting rule(s): - Publish XenApp User Session Details DW (disabled by default, override 'Enabled' parameter) - Publish XenApp User Logon Details DW |
Target | Display Name | Description |
---|---|---|
Citrix XenApp MP Agent Service | Run Check Requirements for Citrix XenApp MP Agent |
Monitor | Management Pack | |
---|---|---|
XenApp Application Accessibility | Citrix Management Pack for XenApp 6.x |
Monitor | Management Pack | |
---|---|---|
Active XenApp Sessions | Citrix Management Pack for XenApp 6.x | |
All XenApp Sessions | Citrix Management Pack for XenApp 6.x | |
XenApp Server Application Enumerations per Second | Citrix Management Pack for XenApp 6.x | |
XenApp Server Application Resolution Time | Citrix Management Pack for XenApp 6.x | |
XenApp Logons | Citrix Management Pack for XenApp 6.x | |
XenApp Installation Drive Free Space Percentage | Citrix Management Pack for XenApp 6.x | |
XenApp Server Filtered Application Enumerations per Second | Citrix Management Pack for XenApp 6.x | |
XenApp Server Load | Citrix Management Pack for XenApp 6.x | |
Total File Count of All User Profiles | Citrix Management Pack for XenApp 6.x | |
Total File Size of All User Profiles | Citrix Management Pack for XenApp 6.x |
Monitor | Management Pack | |
---|---|---|
XenApp ICA Port - Connection Refused | Citrix Management Pack for XenApp 6.x | |
XenApp ICA Port - DNS Resolution Failure | Citrix Management Pack for XenApp 6.x | |
XenApp ICA Port - Host Unreachable | Citrix Management Pack for XenApp 6.x | |
XenApp ICA Port - Connection TimeOut | Citrix Management Pack for XenApp 6.x | |
XenApp IMA Port - Connection Refused | Citrix Management Pack for XenApp 6.x | |
XenApp IMA Port - DNS Resolution Failure | Citrix Management Pack for XenApp 6.x | |
XenApp IMA Port - Host Unreachable | Citrix Management Pack for XenApp 6.x | |
XenApp IMA Port - Connection TimeOut | Citrix Management Pack for XenApp 6.x | |
XenApp Management Console Port - Connection Refused | Citrix Management Pack for XenApp 6.x | |
XenApp Management Console Port - DNS Resolution Failure | Citrix Management Pack for XenApp 6.x | |
XenApp Management Console Port - Host Unreachable | Citrix Management Pack for XenApp 6.x | |
XenApp Management Console Port - Connection TimeOut | Citrix Management Pack for XenApp 6.x | |
XenApp RDP Port - Connection Refused | Citrix Management Pack for XenApp 6.x | |
XenApp RDP Port - DNS Resolution Failure | Citrix Management Pack for XenApp 6.x | |
XenApp RDP Port - Host Unreachable | Citrix Management Pack for XenApp 6.x | |
XenApp RDP Port - Connection TimeOut | Citrix Management Pack for XenApp 6.x | |
XenApp Session Reliability Port - Connection Refused | Citrix Management Pack for XenApp 6.x | |
XenApp Session Reliability Port - DNS Resolution Failure | Citrix Management Pack for XenApp 6.x | |
XenApp Session Reliability Port - Host Unreachable | Citrix Management Pack for XenApp 6.x | |
XenApp Session Reliability Port - Connection TimeOut | Citrix Management Pack for XenApp 6.x | |
XenApp XML Service Port - Connection Refused | Citrix Management Pack for XenApp 6.x | |
XenApp XML Service Port - DNS Resolution Failure | Citrix Management Pack for XenApp 6.x | |
XenApp XML Service Port - Host Unreachable | Citrix Management Pack for XenApp 6.x | |
XenApp XML Service Port - Connection TimeOut | Citrix Management Pack for XenApp 6.x |
Monitor | Management Pack | |
---|---|---|
XenApp Zone Off-line Servers | Citrix Management Pack for XenApp 6.x |
Rule | Management Pack | |
---|---|---|
XenApp Application Event Log Collect - Information (Event) | Citrix Management Pack for XenApp 6.x | |
XenApp Security Event Log Collect - Information (Event) | Citrix Management Pack for XenApp 6.x | |
XenApp Session CPU Utilization (non consecutive) (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp User Session Details DW (Performance DW) (OBSOLETE) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Handle Count (non consecutive) (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Handle Count (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Latency - Average (non consecutive) (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Latency - Average (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Latency - Deviation (non consecutive) (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Latency - Deviation (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Latency - Last Recorded (non consecutive) (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Network Errors (non consecutive) (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Network Traffic (non consecutive) (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Network Traffic (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Page File Size (non consecutive) (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Page File Size (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Session CPU Utilization (Performance DB DW) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Handle Count (Performance DB DW) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Latency - Average (Performance DB DW) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Latency - Deviation (Performance DB DW) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Latency - Last Recorded (Performance DB DW) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Network Errors (Performance DB DW) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Network Traffic (Performance DB DW) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Page File Size (Performance DB DW) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Thread Count (Performance DB DW) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Working Set Size (Performance DB DW) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Thread Count (non consecutive) (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Thread Count (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Session Working Set Size (non consecutive) (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp System Event Log Collect - Information (Event) | Citrix Management Pack for XenApp 6.x | |
Custom File Count of User Profile (Alert) | Citrix Management Pack for XenApp 6.x | |
Executable File Count of User Profile (Alert) | Citrix Management Pack for XenApp 6.x | |
Media File Count of User Profile (Alert) | Citrix Management Pack for XenApp 6.x | |
Custom File Count of User Profile (Performance DB DW) | Citrix Management Pack for XenApp 6.x | |
Executable File Count of User Profile (Performance DB DW) | Citrix Management Pack for XenApp 6.x | |
Media File Count of User Profile (Performance DB DW) | Citrix Management Pack for XenApp 6.x | |
Total File Count of User Profile (Performance DB DW) | Citrix Management Pack for XenApp 6.x | |
Total File Size of User Profile (Performance DB DW) | Citrix Management Pack for XenApp 6.x | |
Total File Count of User Profile (Alert) | Citrix Management Pack for XenApp 6.x | |
Total File Size of User Profile (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Logons (Performance DW) (OBSOLETE) | Citrix Management Pack for XenApp 6.x | |
User Logon Process - Profile loading (Phase 1) Duration (Alert) | Citrix Management Pack for XenApp 6.x | |
User Logon Process - Applying GPOs (Phase 2) Duration (Alert) | Citrix Management Pack for XenApp 6.x | |
User Logon Process - User initialization (Phase 3) Duration (Alert) | Citrix Management Pack for XenApp 6.x | |
User Logon Process - Logon script (Phase 4) Duration (Alert) | Citrix Management Pack for XenApp 6.x | |
User Logon Process - Citrix initialization (Phase 5) Duration (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Process CPU Usage (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Process IO Operations (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Process Page Faults (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Process Page File Size (Alert) | Citrix Management Pack for XenApp 6.x | |
XenApp Process Working Set Size (Alert) | Citrix Management Pack for XenApp 6.x | |
Total File Count of All User Profiles (Performance DB DW) | Citrix Management Pack for XenApp 6.x | |
Total File Size of All User Profiles (Performance DB DW) | Citrix Management Pack for XenApp 6.x | |
Publish Custom User Activity Event Log Messages DW | Citrix Management Pack for XenApp 6.x Reports | |
Publish XenApp Process Details DW | Citrix Management Pack for XenApp 6.x Reports | |
Publish XenApp User Session Details DW | Citrix Management Pack for XenApp 6.x Reports |