Disable vSphere client session timeout for monitoring purposes

 One of the usual ways of monitoring network infrastructures is checking the environment via many web-based consoles, directly in a 24*7 real-time NOC unit. vSphere web client and its built-in Performance section inside the Monitor tab for the VI's components monitoring is one of the most beneficial tools however, you certainly know it will automatically log out and terminate the currently connected session after an idle period. So it's possible to modify the timeout duration via editing webclient.properties file in the VCSA Shell and change the value like the following way:

 

cd /etc/vmware/vsphere-client

vi webclient.properties   

Change the session.timeout value from 120 to 0 if you need to disable the idle timeout logout operation. Then type :wq to save and quit the vi editor.

 

Finally login to the VAMI console (vcsa:5480) and restart the "vsphere client web service", or do it with CLI by running:

service-control --stop vsphere-ui | service-control --start vsphere-ui

 

 

Importance of monitoring virtualized environments

Which factors should we consider as the monitoring metrics?

Choosing between monitoring solutions is one of the important decisions that each IT manager should decide. But before selecting the software/platform, it’s vital to investigate and collect the critical components of infrastructure that we need to monitor. With the growth of virtualization and cloud computing technologies, we have to attend to many aspects, especially physical resources and virtualization components. Analyzing detailed metrics on each of these parts will give us many benefits, like protecting virtual machines against failures and increasing the rate of availability in the virtualization infrastructure. Many factors we need to consider, like the following:

 Physical components:

1. Computing resources consumption: Physical processor and memory   
2. Cluster available capacity: cluster’s resource while the host failures
3. Availability of hosts: ESXi heartbeat issues, failover network infrastructure, and VMkernel settings
4. Storage usage during work hours and backup operations: Datastore IOPS and rate of space usage
5. Over-allocation & under-allocation of each physical resources: CPU, RAM, NIC, Disk
6. Memory ballooning and dedicated datastores for swap files

Virtual components:

1. Extra VM log files and their unexpected storage usage
2. Not-installed VMware Tools or old version of them that are installed on the virtual machines
3. Old-remained snapshots and many parent-child VMDK files
4. Inactive or unused virtual machines  
5. Not-used mounted ISO files and old connected physical media
6. Orphaned VM files, especially VMDK files
7. Rate of VM’s memory swapping and overall memory performance

 

Although some of these issues are very easy to resolve, they’re required a real-time 24*7 monitoring system also dedicated response teams for proper reactions against possible or even unexpected problems. Regardless of chosen monitoring solutions in your infrastructure, it’s more important to have some well-done plans for counterattacks against forecasted challenges, availability issues, and every detected incident that causes many risks against our infrastructure or data center.