Total Logon Time metric display "No Data" in vRops for Horizon dashboard

Last week I was working with one of my customer who has recently upgraded their vRops environment to 6.7 version. Their environment consist of VDI environment running on VMware Horizon.

Here in vRops environment they have default Horizon dashboard as they have configured Horizon adapter for their VDI environment.

From some time we are getting issue into Horizon dashboard where they were not able to see Total Logon Time metric display where its display "No Data" as seen below

To resolve the issue of " No Data" there is a solution which works for me and recommended by VMware.

This issue identified when we not enable the time profiler. The logon time is calculated by 'First_idletime - logon_starttime'

The 'logon_starttime' is retrieved from DB and 'first_idletime' is retrieved from DA (Desktop agent).

Its because the DB is not consistent with DA. This will cause the "logon_startime" be smaller then 'first_idletime'. And the total_logon time will be negative. Adapter will drop this negative value, so this is were we cannot see this metric.

We can resolve this issue by two ways.

1) Sync the database clock (Horizon event database) with broker server (Horizon Connection server).

2) Enable timing profiler by running : "vdmadmin -I -timingProfiler -enable" in the connection server.

After applying the suggested suggestion, Total Logon Time matrix populated successfully.

Please find VMware KB article associated for this issue.

Keep sharing.... :)

Comments

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out. Now the option left is from the command line of VCSA appliance. Below steps will make it possible to change the FQDN of the VCSA from the command line. Access the VCSA from console or from Putty session. Login with root permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot the VCSA appliance. After reboot you will be successfully manage to change the FQDN of the VCSA . Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client. If you are using self-signed certificate, you can regenerate the certificate with...

VCF 9 Networking : Centralized vs Distributed Connectivity

VCF 9 Networking : Centralized vs Distributed Connectivity With the release of VMware Cloud Foundation 9 (VCF 9.0) , VMware has redefined the private cloud networking model by introducing both centralized and distributed connectivity. This dual approach provides flexibility for organizations to choose between traditional edge-based routing and modern, host-level distributed networking. Why New Networking in VCF 9? Prior to VCF 9, NSX networking was largely edge-centric—requiring dedicated Edge clusters to handle north-south traffic. This created scaling and operational overheads. VCF 9 introduces a cloud-like networking abstraction with: Native VPCs (Virtual Private Clouds) for tenant isolation. Transit Gateways (TGW) to interconnect VPCs and external networks. Simplified bootstrapping – NSX VIBs are embedded in ESXi for easier enablement. Improved lifecycle and visibility via integrated VCF Operations. These enhancements align with VMware’s goal of offer...

High-Speed Networking for VMs: VMXNET3 Now Supports Up to 65 Gbps

The VMXNET3 adapter is VMware's high-performance virtual network adapter, designed for optimized performance in vSphere environments. It is the default and recommended adapter for most modern workloads on ESXi , delivering high throughput, low latency, and support for advanced networking features. With the release of vSphere ESXi 8.0 Update 2 , VMXNET3 introduces new capabilities that significantly enhance virtual network performance. What’s New in ESXi 8.0 Update 2 for VMXNET3? Traditionally, VMXNET3 reports a default link speed of 10 Gbps to the guest operating system. However, the actual achievable throughput often exceeds this value—thanks to technologies such as multi-queue support , Receive Side Scaling (RSS) , and Large Packet Offload . Starting with ESXi 8.0 Update 2 , this limitation can now be overridden , and VMXNET3 can be configured to support custom link speeds of up to 65 Gbps . This enhancement enables improved flexibility and throughput for high-performance w...

Search This Blog