Home
Vmware-Monitor-Features
Vmware-Monitor for Xymon (VMX)
intro | features | requirements | license | screenshots | download features
Core features of
Vmware-Monitor for Xymon (VMX):
- supports VMware ESX 3.5/ESXi 3.5, ESX 4.0/ESXi 4.0 (vSphere), ESX 4.1/ESXi 4.1 (VMware-server-2.0.x unofficially supported by vMA 4.0 w/o SP)
- no modification on VMware hosts needed (no support/warranty implications)
- uses official method provided by VMware (again: support-friendly)
- current CPU- and memory-usage, both of the ensemble of all VMware hosts, for each individual host and each running VM (and graphical trending of these and more of course)
- warning if a host is in maintainance-mode or has the "reboot-needed" flag set
- tracking of VM start/stop/move on each VMware host (no matter if the VM was moved by vmotion, DRS, manually added/removed). So it's possible to easily determine when a VM was started or stopped on (or moved to) a particular host.
- vMEM/pMEM-ratio, i.e. how much of the physically available RAM is assigned to the running VMs per VMware host
- one-click overview/summary of the complete monitored VMware environment on one overview-page with the following data:
- For each VMware host monitored overview-line with the following metrics is available:
- number of running VMs (and vCPUs)
- available CPU and RAM-resources
- current CPU- and RAM-usage
- number of monitored VMware hosts
- total CPU (MHz) available
- CPU used
- software version/patch-level of each VMware host
- CPU model
- A summary of all monitored hosts is available with the following data:
- total vCPU-count running
- total physical RAM available
- virtual RAM used
- overview-page for each VMware host along w/ it's status and the currently running VMs
- central configuration of VMware-monitoring on the Xymon server
- perfect integration with Xymon/Hobbit monitoring system
- easy, quick and clean (non-intrusive) installation
- ressource friendly: low monitoring overhead due to non-forking design on the server-side and minimized disk-access to avoid I/O problems