You are here

vSphere Resource Pool Monitoring

Requires Opsview 6.2

This Host Template is part of the Vmware Vsphere Opspack

check_circle
Opsview Supported

404: Not Found

Included in the OS - VMware vSphere Opspack

Host Template: OS - VMware vSphere ESXi Resource Pool

Monitor your ESXi Resource Pools with a variety of checks including CPU Usage, Memory Usage and Memory Ballooning. This Host Template includes support for VMware vMotion, so you can keep monitoring Resource Pools even if they are moved between Hosts with no change to your Opsview configuration.

This Host Template includes the following Service Checks:

Service Check Name Description Default Thresholds (Warning, Critical) UOM
vSphere - Resource Pool - CPU Used CPU Used in MHz. N/A MHz
vSphere - Resource Pool - Memory Used Amount of host physical memory consumed, and the amount used for virtualization infrastructure. N/A B
vSphere - Resource Pool - Memory Balloon Amount of memory allocated by the Virtual Machine memory control driver, which controls ballooning. N/A B

Usage Instructions

NOTE: To monitor a Resource Pool within a Cluster, the Cluster must contain Hosts.

vMotion Support

To allow for vMotion support (moving Resource Pools between ESXi Hosts without having to update your Host details), you must use the vCenter Credentials Variable listed in Step 2. Additionally, all Hosts utilized in vMotion must share login credentials to allow Opsview to maintain monitoring. The ESXi Host Name is optional if using vCenter Credentials.

When using vMotion, the ESXi Host containing the requested resource can be found automatically without needing to specify the Host the resource is on. However, this automatic retrieval of the Host will extend the runtime of the service checks and if performance is a concern, the Opsview Host configuration should be updated with the correct ESXi Host details.

Providing the vCenter Credentials variable will also allow for enhanced error handling when carrying out Service Checks.



Step 1: Add this Host Template

Add the OS - VMware vSphere ESXi Resource Pool Host Template to your Opsview Monitor host. If the resource you're monitoring has no hostname or public IP, then open the Advanced settings pane and change Host Check Command to Always assumed to be UP.

For more information, refer to Opsview Knowledge Center - Adding Host Templates to Hosts.



Step 2: Add and configure variables required for this Host Template

The Service Checks in this Host Template use the following variables, and they will be added to your Opsview Monitor instance when you import the Opspack:

VSPHERE_ESXI_RES_POOL_NAME

| Parameter | Position in Variable | Name | Description | |:---------:|:--------------------:|:-----|:------------| | --esxi-res-pool-name | Value | ESXi Resource Pool Name | Name of the ESXi Resource Pool |

VSPHERE_ESXI_CREDENTIALS

| Parameter | Position in Variable | Name | Description | |:---------:|:--------------------:|:-----|:------------| | --esxi-username | Arg1 | ESXi Username | Username for the ESXi Host | | --esxi-password | Arg2 | ESXi Password | Password for the ESXi Host |

VSPHERE_ESXI_HOST_NAME

| Parameter | Position in Variable | Name | Description | |:---------:|:--------------------:|:-----|:------------| | Opsview UI Only | Value | ESXi Host Display Name | Display Name for ESXi Host Service Checks | | --esxi-hostname | Arg1 | ESXi Host Name | Name of the ESXi Host |

VSPHERE_VC_CREDENTIALS

This variable is optional and only required to allow for enhanced error handling when carrying out Service Checks.

Parameter Position in Variable Name Description
--vcenter-username Arg1 vCenter Username Username for vCenter instance
--vcenter-password Arg2 vCenter Password Password for vCenter instance
--vcenter-server Arg3 vCenter Instance Name Name of the vCenter instance


For more information, refer to Opsview Knowledge Center - Adding Variables to Hosts.

For mode-specific help, run the plugin with the -h -m <mode> flags. This will list the required and optional Variable Arguments for that mode. The appropriate mode for each Service Check is listed here:

Service Check Name Mode
vSphere - Resource Pool - CPU Used ESXiResPool.CPU.Used
vSphere - Resource Pool - Memory Used ESXiResPool.Mem.Used
vSphere - Resource Pool - Memory Balloon ESXiResPool.Mem.Balloon

SSL Certificates

Additionally, you can use the following variable to pass in your SSL certificates for use when connecting to the service provider to gather metrics:

VSPHERE_CERTIFICATES

Parameter Position in Variable Name Description
--ca-path Arg1 CA Certificate Path Path to the CA Certificate
--client-cert Arg2 Client Certificate Path Path to the Client Certificate
--client-key Arg3 Client Key Path Path to the Client Key



Step 3: Apply changes and the system will now be monitored

View Output

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