Mini-specification v1.0

What's affected:

• common code for Server and Proxy

New parameter in vmware.eventlog item

A new optional parameter <severity> should be added to item vmware.eventlog.
vmware.eventlog[<url>,<mode>,<severity>]

This parameter should specify the severity of events, which should be logged.

<severity> should be of a string type. Possible values are

• error
• info
• user
• warning

Multiple values must be separated with commas and quoted. If no value is specified, then events should be logged regardless of their severity. If an invalid value is specified, then vmware.eventlog item should become invalid, no events should be collected, and an error message should be displayed near the item.

The request of type CreateCollectorForEvents(createCollector) should be modified in src/zabbix_server/vmware/vmware.c. The parameter filter should be extended with zero or more entries of category based on user input of argument "severity" of item "vmware.eventlog".

Extend the event description in "Monitoring -> Latest data" in column "value"

1. Add event type like so:

If "eventTypeID" is defined for the event, then the line should be "eventTypeID: <value>", where <value> is the "eventTypeId" property.

Otherwise, the line should be "type: <severity>/<value>", where <value> is the event type.

2. Add a line "target: <value>" "source: <value>". Initially I planned to call it "target" like in vCenter. However, when I started implementation, I discovered that it is already present in Zabbix and it is called "source" in Zabbix.

Before the change, it was capable of showing datacenter/computeResource/host for events originated from hosts and IP for all other events.

After the change, value should be a list of names of the following properties in the following format:

source: datacenter/computeResource/host/vm ds:xxx net:xxx dvs:xxx

Only the properties that are defined should be written if they are present.

Limitations

First, with the current architecture, an event can be collected only once. So it is impossible to create more than one vmware.eventlog item so that they do not interfere with each other. Second, if severity of events is specified in vmware.eventlog item, only events with the specified severity are collected. This is the reason we are not going to implement any filters except severity at the stage of collecting VMware events.

Extended filtering would be possible using dependent items derived from vmware.eventlog using regexp. Such items should be created in user templates.

Signoff:

MVekslers	-1.0
natalja.zabbix	-1.0

Available in versions:

• pre-7.0.0alpha7 2f0b653509a,  090af355e27

Updated documentation:

• vmware.eventlog item
• What's new