How vCenter events are processed

The instance converts the subscribed vCenter events into ServiceNow system events (sysevent) that the system uses to perform tasks, such as email notification.

Event processing

The MID Server listens for the vCenter events configured in the vCenter Event Collector form. When one of these events is returned from vCenter, the instance parses the payload with a business rule that converts the vCenter event into a ServiceNow system event. The resulting sysevents contain these values:
  • Name: Name of the ServiceNow system event created from the vCenter event. This value is always automation.vcenter.
  • Parm1: vCenter event that was returned. This event must be associated with an event collector record.
  • Parm2: Event data provided by vCenter, in JSON format.
Figure 1. Log entries for vCenter events
Log entries for vCenter events

Handling custom vCenter events

To configure your instance to handle vCenter events not supported in the base system:
  • Add the vCenter events to a vCenter Event Collector record. Click the Edit button in the vCenter Event related list and select the events from the list. This can be the same collector record as the one containing the supported vCenter events, but only if the same MID Server is used to gather the events. Multiple MID Servers can listen to the same vCenter instance, but each MID Server can only have one event collector record.
  • Create a new script action to process the vCenter events. For instructions, see Script actions. As a reference, the instance processes the vCenter events in the base system with a script action called Discovery: Process vCenter events. Do not edit or delete this script action.
  • In addition to Script actions, you can create and trigger email notifications for the same system event.

For the list of supported vCenter events, see Configure the vCenter event collector extension.