Monitoring a Horizon client session to a Global Entitlement requires a slightly different approach, due to the fact that one Horizon pod could be brokering a connection for desktops in another. Consider the following scenario:
A user with the RTP home site assignment connects to the Horizon pod in San Jose, and is connected to a desktop in the RTP pod.
If you reviewed the Monitoring - Sessions window in the RTP pod, you might expect to see the connection to the desktop. This is not how it works in a Cloud Pod; the session data is maintained by the pod the user initially connected to, not the one where their desktop is hosted (we are assuming they are different for this example). Additionally, the Monitoring - Sessions window is not Cloud Pod-aware; unless you know where Horizon pools were actually located, you wouldn't...