Skip to main content

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

Post a Comment

Popular posts from this blog

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 the
2 comments
Read more

Issue : Configure Management Network option is Grayed out into ESXi

Last week I got into an issue of one of my client into Vsphere environment where one of its ESXi went done out of the network. Issue was IP address was showing 0.0.0.0 on main Esxi screen and when I tried to change the network configuration, its " Configure Management network option was greyed out.  I tried to gid into it and try to analyis its vmKernal and vmwarning logs. What I found is its VMkernal switch got removed due to unexpected reason. So to resolve the issue I tried to reconfigure its vswitch0 (vmk0) by going into Tech Mode of that Exi. Below are the steps which I followed to resolve the issue. 1) Login to ESXi 2) Press F2, Check if you " Configure Management network " is greyed out or not" if yes,    follow below 3) Press ALT+F1 to move the ESXi screen to tech mode   ( This is command line like dos) 4) login with root account 5) Run the following command into it esxcli network ip interface add --interface-name= vmk0
2 comments
Read more

Collecting Logs from NSX-T Edge nodes using CLI

  This article explains how to extract the logs from NSX-T Edge nodes from CLI. Let's view the steps involved: 1) Login to NSX-T  Edge node using CLI from admin credentials. 2) Use of  " get support-bundle " for Log extraction. get support-bundle command will extract the complete logs from NSX-T manager/Edge nodes. nsx-manager-1> get support-bundle file support-bundle.tgz 3) Last step is to us e of " copy file support-bundle.tgz url " command. copy file will forward your collected logs from the NSX-T manager to the destination(URL) host from where you can download the logs. copy file support.bundle.tgz url scp://root@192.168.11.15/tmp Here, the URL specified is the ESXi host ( 192.168.11.15) under /tmp partition where logs will be copied and from there one can extract it for further log review. Happy Learning.  :)
Post a Comment
Read more