Get Started Knowledge Base FAQs Troubleshooting Latest Release
Submit a Ticket

Menu

    Citrix Virtual Application (XenApp) Monitoring

    Avatar
    Tier3

    Citrix XenApp monitoring rules allow one to monitor Citrix users, sessions and server health thresholds using our Goliath Intelligent Agent to alert on specified conditions in real-time.

    By default, when the Citrix Virtual Application API is enabled, there are a number of monitoring rules that will be created out of the box in which you can modify and enable for alerting.

    • Citrix XenApp - Session & Server Performance
      • This rule monitors ICA Latency & RTT, Network Latency, Server Load, Users and Sessions
    • Citrix XenApp - Server Not Configured Properly
      • This rule monitors for XenApp Server reporting a Load of 20000
    • Citrix XenApp - Restricted Rights Run of QFARM
      • This rule monitors for XenApp Server reporting a load of 99990
    • Citrix XenApp - No Load Evaluator Configured
      • This rule monitors for XenApp Server reporting Server Load of 99999
    • Citrix XenApp - Full Server Load
      • This rule monitors for XenApp Server reporting a Server Load of 10000

    If you would like to monitor server registration status see article Citrix VDA Registration Alerting

     

    Create a New Monitoring Rule

    1. To create a new monitoring condition for Citrix Virtual Apps, navigate to the Management - Monitors page and click the New button.
    2. For the Group dropdown, select a group in which to store the rule. This is for organizational purposes in the Monitors display.
    3. From the Type dropdown, select the Citrix XenApp monitor you would like to create.
    4. Name the Monitoring Rule via the Name field, as well as define the description and the severity.
    5. In the Devices tab, select the devices to assign to the monitor.
      1. Please note, a machine can only be applied to one VMware ESX/ESXi Host monitoring rule type at a time.
    6. Use the Options tab to define condition(s) to be monitored.
      1. Please note - only the rule type for Citrix XenApp Session has configurable thresholds, all other XenApp rule types have their thresholds hard coded. If you selected one of the hard coded rules you can skip the next step.
      2. Only fields with values will be monitored. If you do not wish to monitor a particular metric do not enter a value in the field. The monitoring rule will trigger on a per metric basis as applicable.
      3. In the ICA Latency field, define the threshold for ICA Latency in which you'd like to monitor
        1. Optionally, next to the field define a Duration value that needs to be exceeded in order to alert 
      4. In the ICA Roundtrip field, define the threshold for ICA Roundtrip in which you'd like to monitor
        1. Optionally, next to the field define a Duration value that needs to be exceeded in order to alert
      5. In the Network Latency field, define the threshold for Network Latency in which you'd like to monitor
        1. Optionally, next to the field define a Duration value that needs to be exceeded in order to alert
      6. In the Server Load field, define the threshold for Network Latency in which you'd like to monitor
        1. Optionally, next to the field define a Duration value that needs to be exceeded in order to alert
      7. In the Logon Duration field, define the length of the logon time in which you'd like to monitor
      8. In the Active Sessions field, define the threshold of Active Sessions in which you'd like to monitor
      9. In the Active User field, define the threshold of Active Users per server in which you'd like to monitor
      10. In the Active Sessions field, define the threshold of Active Sessions per server in which you'd like to monitor
    7. The Schedule tab of a monitoring rule allows users to define how frequently the rule will alert. This can be done by adjusting the following fields:
    • Alert Every Time: Defines whether an alert is generated every time the conditions are on the previous tab are met.
      • When checked, an alert is generated every time the specified condition is met.
      • When unchecked, the alert is only generated if the alert conditions are met, and the Minimal Notification Interval, see below, is exceeded since the last alert for this type.
    • Minimal Notification Interval: Defines the minimum amount of time that must elapse between events for the specified condition before another alert will be generated.
      • For example, if the interval is 15 minutes and the condition is being met every 3 mins, you will receive 1 alert every 15 minutes instead of being alerted at each occurrence.
        • However, each alert occurrence is considered unique based on the details. For example, an Event Log alert is considered the same based on being the same Event Type and ID, from the same server/workstation.
      • The Alert Every Time checkbox must be unchecked in order to use this option.
      • For ServerWatch IP Services, this also defines the minimum elapsed time since a service is first detected as down or failed before an alert is generated.
    • Maximum Notification Interval: Defines the maximum number of times you want to be notified during a continuous failure situation.
      • The default value of '0' means infinite; no maximum is defined so you will continue to be notified according to your Alert Every Time and Minimal Notification Interval settings.
      • A non-zero value means that after you have been notified the number of times defined in the Maximum Alert Notifications, and according to your Alert Every Time and Minimal Notification Interval settings, you will not be notified again.
        • For example, if "5" is selected, the event will alert for the first 5 events and all additional events will be ignored.
    • Notify On Restore: Defines whether a 'Restore' alert is generated if you have previously been alerted due to a failure.
      • For example, if CPU has been 90%, and then dropped below the alert threshold, the notify on restore email will inform you that the condition has returned to a normal state.
      • There is always a Notify on Restore for a ServerWatch type alerts.
    • Service Check Frequency, Every: Defines the frequency with which the service specified for this Monitoring Rule is checked. It is no recommended to do this check any fewer then 3 mins. 
    • Alert 1st Time After X Failures: Define a value 1 or greater that defines how many successive failures should occur before the 1st alert notification 'Action' is executed.
      • The Alert Every Time and Minimum Notification Interval settings do no become applicable until after this threshold setting is exceeded.
      • The default value for this setting is blank which means not applicable. When not applicable, the Alert Every Time and Minimum Notification Interval settings are active immediately and the 1st alert does not occur until the Minimum Notification Interval threshold is equaled or exceeded if it is active.

    Additional Configuration

    For additional configuration options please see the following articles: