Skip navigation
Currently Being Moderated

63.1 About

VERSION 4  Click to view document history
Created on: Oct 12, 2010 6:08 PM by Zenoss API - Last Modified:  Oct 12, 2010 6:22 PM by Zenoss API

 1. About

With Zenoss, you can collect information to monitor your VMware infrastructure. By entering a single set of connection parameters, you allow Zenoss to:

  • Obtain the names and properties of various entities in your VMware infrastructure

  • Monitor metrics collected by VMware

  • Retrieve VMware events

Zenoss extracts VMware information through the VMware Infrastructure (VI) SDK, VMware's SOAP interface to its line of server virtualization products. The SDK can be accessed from an individual ESX server or vCenter Server (previously, VirtualCenter Server) instance, which can return information about many ESX servers.

For more information about VMware infrastructure, see VMware's Introduction to VMware Infrastructure

 1.1. VMware Events

VMware records a wide range of events that are available through the VI SDK. Zenoss extracts these events and makes them available in the event console.


Figure 63.1. VMware Events (Event Console)

VMware Events (Event Console)

The device column shows the ID of the VMware entity with which the event is associated, unless the event is specific to a guest VM. In that case, the Device column shows the ID of the host, and the Component column displays the ID of the guest.

Zenoss maps the VMware event to the event class and assigns the event a severity level. The event class appears in the Event Class column.

To see detailed event information and the original VMware event type, double-click the event row.

The VMware event type is the value shown for eventGroup.


Figure 63.2. Event Details

Event Details

 1.1.1. Migration Events

When a VMotion guest migrates from one host to another, VMware records events to signal its progress. When a VmMigrated event occurs, it is duplicated to become two events, which are mapped to the /VMware/Migration event class in Zenoss. One event contains the originating host as the device; the other lists the destination host as the device.

An event command (navigate to Events > Event Manager, and then select Commands in the left panel) reacts to these events by remodeling the two hosts and generating an updated view of the guests. The time required to produce updated guest lists (from the time migration completes) is between 30 seconds and four minutes.

Comments (0)