The total logon time metric is calculated differently depending on your Horizon configuration.
To ensure that the total logon time is calculated correctly, ensure that the system clock of the event database has been synchronized with the Horizon Connection Server instance. In addition, enable the timing profiler on the Horizon Connection Server instance if possible.
If the timing profiler on your Horizon Connection Server instance is not enabled, vRealize Operations for Horizon calculates the total logon time using the following process:
- The vRealize Operations for Horizon broker agent reads the event database to obtain the time that a user requests a Horizon desktop or application. This time is saved as the session|Logon Triggered Timestamp metric.
- The vRealize Operations for Horizon desktop agent monitors the Windows login process and notifies the adapter when the process is finished. This time is saved as the session|First Idle Timestamp metric.
- vRealize Operations for Horizon calculates the total logon time by subtracting the value of the session|Logon Triggered Timestamp timestamp from the value of the session|First Idle Timestamp.
The limitations of this method of calculation can be overcome by enabling the timing profiler. To do so, run the vdmadmin -I -timingProfiler -enable command on the Horizon Connection Server instance. For more information, see Using the vdmadmin Command in the Horizon 7 Administration guide.
Once the timing profiler is enabled, the vRealize Operations for Horizon broker agent reads the total logon time from the event database. With this method, vRealize Operations for Horizon obtains the total logon time from Horizon instead of calculating it independently.
