Monitoring the Citrix Delivery Controller 5

eG Enterprise offers a 100%, web-based Delivery Controller- 5 model (Figure 3) to continuously monitor the broke and to proactively alert administrators to potential issues in its performance.

Figure 3 : Layer model of the Citrix Delivery Controller 5

The metrics mapped to every layer of this model enable administrators to find quick and accurate answers to the following performance queries:

  • Is the broker able to connect to the hosting server?
  • Is any hosting server in the maintenance mode? If so, which one?
  • Have any controllers in the farm failed? If so, which ones?
  • Is the controller being monitored operating without glitches?
  • Are any controllers in the farm in a powered-off state? If so, which ones?
  • Is the controller being monitored in a powered-on/off state currently?
  • Are the critical site services running across the farm? Are they inactive on any controller in the farm? If so, which ones?
  • Are the critical site services running on the controller being monitored?
  • How healthy are the interactions between the broker's MS SQL database and critical Citrix services such as the Broker service, the Configuration service, the Host service, the AD Identity service, the Machine Creation service, and the Machine Identity service? Is any service unable to access the database, or is any service experiencing slowdowns while executing database transactions? Which one of these services is in an abnormal state currently?
  • Have the broker's logs captured any errors/warnings recently?
  • Is any desktop unable to register with the broker? If so, which one?
  • How many catalogs have been configured on the broker? What are they? What is the type of each catalog?
  • Have physical machines been included in any catalog? If so, which catalog is it?
  • How many desktops in each catalog have been assigned to users, and how many are unassigned?
  • Does any catalog consist of desktops that do not belong to any desktop group?
  • Is the License server available in the site?
  • Is the broker able to connect to the SQL database server?
  • Is any desktop group in maintenance mode?
  • Is any desktop group unavailable?
  • Are there adequate idle desktops in every group, or is any group over-utilized?
  • Have any desktops disconnected from their groups? Which groups have such disconnected desktops?
  • Does any desktop group consist of unregistered desktops?
  • Which desktop group is managing CPU-intensive desktops? Which desktops are these? Which controller is managing these desktop groups?
  • Are too many desktops in a group experiencing network latencies?
  • Did the connection attempt to any desktop fail recently? If so, which desktop is this? Which desktop group and controller are managing this desktop?
  • Are any desktops in a group powered off currently?
  • Is the broker overloaded with sessions?
  • Have published applications been accessed in any session?
  • Have too many user sessions disconnected from the broker?
  • Are too many sessions to virtual desktops logging out?
  • Is any desktop in an Unavailable state currently?
  • Is the virtual desktop agent unavailable on any desktop?
  • Is any desktop in the maintenance mode?