Administration

Table Of Contents
Configuring VMware Horizon Performance Tracker
You can run Horizon Performance Tracker in a remote desktop. You can also run Horizon
Performance Tracker as a published application.
Horizon Performance Tracker Features
Horizon Performance Tracker displays critical data of the following features:
Table 11-13. Horizon Performance Tracker Features
Performance Monitoring Details
Protocol specific data n Encoder Name: The name of encoder used in display
protocol
n Bandwidth Used: Overall bandwidth for incoming
and outgoing bandwidth averaged over the sampling
period for display protocol, PCoIP or Blast
n Frame rate per second: Number of imaging frames
that were encoded over a one-second sampling period
n Audio On: Whether the Audio feature is on
n Audio Started: Whether the Audio feature is started
n CPU usage:
n Encoder CPU: CPU usage of the display protocol
encoder in current user session
n System CPU: Total CPU usage of system
Transport type n Client to Remote Session: UDP or TCP protocol
transport package used from client to remote peer
n Remote Session to Client: UDP or TCP protocol
transport package used from remote peer to client
n Horizon Connection Server: UDP or TCP protocol
transport package used to connect to a Connection
Server instance
System health status n Estimated Bandwidth: Overall estimated bandwidth
available between Horizon Client and Horizon Agent
n Round Trip: Round trip latency in milliseconds between
the Horizon Agentand the Horizon Client
Session context n Server details, such as DNS name, domain name,
whether it is tunneled, URL, remote IP address
n Client machine details, such as display number, IP
address, keyboard and mouse layout, language, time
zone
Realtime protocol switch
Note Horizon Performance Tracker only collects and displays data when Horizon Agent is
running in a virtual desktop session.
System Requirements for Horizon Performance Tracker
Horizon Performance Tracker supports these configurations.
Horizon 7 Administration
VMware, Inc. 239