You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use Case: As a vspherdb user i want to troubleshoot performance issues of virtual machines with vspheredb. In the form of the "Virtual Machine" it would be useful to find the information of the CPU usage and capacity of the underlaying ESX machine.
This avoids me to click for each Virtual Machine to the related form of the ESX host.
Current Behavior
On ESX host view on RAM usage a tooltip provides additional infos.
Possible Solution
It would be nice to provide this info also for CPU usage on ESX host
An additional value would be provided to an VMWare administrator, when the box indicating the cpu usage in the Form "Virtual Machine" would provide also the cpu usage in % and Mhz of the underlaying esx host.
A possible solution could be to display the related information as Tooltip in the tab "virtual machine" on top of the box vm CPU usage.:
The text was updated successfully, but these errors were encountered:
Expected Behavior
Use Case: As a vspherdb user i want to troubleshoot performance issues of virtual machines with vspheredb. In the form of the "Virtual Machine" it would be useful to find the information of the CPU usage and capacity of the underlaying ESX machine.
This avoids me to click for each Virtual Machine to the related form of the ESX host.
Current Behavior
On ESX host view on RAM usage a tooltip provides additional infos.
Possible Solution
It would be nice to provide this info also for CPU usage on ESX host
An additional value would be provided to an VMWare administrator, when the box indicating the cpu usage in the Form "Virtual Machine" would provide also the cpu usage in % and Mhz of the underlaying esx host.
A possible solution could be to display the related information as Tooltip in the tab "virtual machine" on top of the box vm CPU usage.:
The text was updated successfully, but these errors were encountered: