The Controllers Layer

Using the tests mapped to this layer, you can easily determine the following:

  • What is the state of each broker?;
  • How many machines are registered with each broker?;
  • The overall health of the broker in terms of how error-prone it is;
  • The issues in the communication between the Citrix Configuration Service and the MS SQL database;
  • Errors in transactions executed by the Citrix Host Service on the broker’s database;
  • How well the Citrix AD Identity Service interacts with the broker’s MS SQL database?;
  • The health of transactions performed by the Machine Creation Service on the broker’s database;
  • Whether the Citrix Machine Identity Service is able to connect to the broker’s database, and how well the database is managing the load generated by the service;
  • The load handling ability of the Citrix XML Service that is responsible for communication between the Web Interface component and the XenDesktop site;

Since most of the tests mapped to this layer are already discussed in the Monitoring Citrix Delivery Controller v3/4 and Monitoring Citrix Delivery v5 chapters, let us now proceed to discuss those tests that haven’t been dealt before.

Tests associated to Controllers layer

Figure 1 : The tests mapped to the Controllers layer