Veeam Software, a business continuity product company for virtualization, has a complete list of vCenter Events sorted by ID. Here’s the first event in the list:

 
Clicking on the ID starts a javascript popup with event details:

Event: AccountCreatedEvent

Cid: ‘200’
ManagedObject: ‘VC’
MessageGroup: ‘MsgGroupHost’
OptionVar: ‘EventId=”${eventid}” Timestamp=”${timestamp}” ComputeResource=”${computeresource}” Datacenter=”${datacenter}” HostName=”${hostname}” Server=”${server}” Username=”${username}” DisplayName=”${vm.name}” UUID=”${vm.uuid}”‘

This event records that an account was created on a host.

Here’s the event when the new ESXi 5.0 syslogd service is unable to communicate with syslog (KB 2003127):

 
This is an important change from prior versions of ESXi, which would not stop logs on an error (note the “Since 5.0” in the Message Catalog Text field). An alarm for this event can easily be created by using “esx.problem.vmsyslogd.remote.failure” as the trigger.