You are here

VMware vSphere Monitoring

Requires Opsview 6.2
check_circle
Opsview Supported

404: Not Found

v2.0.1

OS - VMware vSphere Opspack

VMware is considered a leading pioneer in virtualization, allowing users to virtualize everything from computing to the data center, and even extending into cloud and mobile devices. This constant evolution of all things virtual is intended to help users become more agile, responsive and profitable in their day-to-day work and helps them achieve business requirements.

What You Can Monitor

This Opspack provides Host Templates allowing you to monitor your VMware vSphere ESXi Hosts, Guests, and Datastores, as well as constructing generic monitoring queries to run against your instances.

Host Templates

The following Host Templates are provided within this Opspack. Click the name of each Host Template to be taken to the relevant information page, including a full Service Check description and usage instructions.

Prerequisites

  • vSphere 6.0 or vSphere 6.7, other versions supported by pyVmomi include 5.5, 5.1 and 5.0, these and alternative versions may be compatible but are not officially supported.
  • To utilize all Service Checks within the OS - VMware vSphere ESXi Guest Host Template, ensure you have VMware Tools installed on each Guest you want to monitor.
  • vMotion support and the vCenter Host Template are only available with a vCenter environment.
  • The following permissions are required for the VMware vSphere Credentials:
Credentials for Privilege Name Description
vCenter Global > Act as vCenter Server Allows Automonitor Scan to discovery ESXi Hosts, VMs, Datastores, Resource Pools and other VMware elements through vCenter.

Allows Opspacks to be informed of vMotion send and receive operations.
ESXi Root >
  • Alarm
  • Datacenter
  • Datastore
  • HealthUpdateProvider
  • Performance
  • System
  • VirtualMachine

| Allows Automonitor Scan to discovery ESXi Hosts, VMs, Datastores, Resource Pools and other VMware elements through ESXi.

Allows relevant Host Templates to be allocated and Service Checks to retrieve metrics for the discovered resources. |

NOTE: If the ESXi user to be used for monitoring is part of a role with lower privileges than root (e.g. read-only), it needs to be added to the SystemConfiguration.Administrators group.
If the VMware server account DOES NOT have the right permissions, VMware Service Checks will fail.

Importing this Opspack

Download the os-vmware-vsphere.opspack file from the Releases section of this repository, and import it into your Opsview Monitor instance. Now you can add the Host Templates you want following the info links in the table at the top.

For more information, refer to Opsview Knowlege Center - Importing an Opspack.

v2.0.0-opsview-6

Bug fixes

  • ODI-3726 Integrate cachemanager with Vsphere and VCenter
  • ODI-3939 fix ssl certificate usage logic
  • ODI-3741 Fix vSphere performance counter metrics bug
  • ODI-3558 Update documentation
  • ODI-3680 Fix vCenter checks not returning data
  • ODI-4131 Add handling of 400 errors and handle cachemanager returns better
  • ODI-4194 Bump min version to 6.3.1
  • ODI-4147 Fix datacenter referenced before assign
  • ODI-2906_Add-supported-version-numbers-to-README

v1.3-opsview-6

ODI-3901 Fix bugs

  • ODI-3740 vSphere-Guest-Memory Used Bug
  • ODI-3901 Fix health checks returning critical

v1.1-opsview-6

ODI-3727 Vmware-vSphere Opspack

Update for Vmware-vSphere Opspack

v1.0-opsview-6

ODI-2906 Vmware-vSphere Opspack

Initial release for Vmware-vSphere Opspack