Veeam Base Discovery

Top  Previous  Next

Target

Monitor/Alert Name

Warning event ID

Error event ID

Close Event ID

Enabled

Overrides

Monitoring Group

Veeam VMware Collector: Monitoring Group has no available Collector(s)


EventDisplayNumber Equal 1305
AND
$Target/Property[Type="System!System.Entity"]/DisplayName$

EventDisplayNumber Equal 1207

yes

no

Veeam Collector Heartbeat

Veeam VMware Collector: Heartbeat Status of Collector Service


EventDisplayNumber Equal 1203

EventDisplayNumber Equal 1207

yes

no

Veeam Virtualization Extensions Service

Veeam Management Pack: License Alert

EventDisplayNumber Equal 1100

EventDisplayNumber Equal 1101

EventDisplayNumber Equal 1103

yes

no

Veeam Virtualization Extensions Service

Veeam VMware Collector: Extensions Service status


Service NotRunning

Service Running

yes

no

Veeam Virtualization Extensions Service

Veeam VMware Collector: Licensed socket count exceeded


EventDisplayNumber Equal 1102

EventDisplayNumber Equal 1104

yes

no

Veeam VMware Collector Service

Veeam VMware Collector: Application Error



TimerWaitInSeconds: 86400

yes

no

Veeam VMware Collector Service

Veeam VMware Collector: Application Warning



TimerWaitInSeconds: 86400

yes

no

Veeam VMware Collector Service

Veeam VMware Collector: Cannot connect to Veeam Extensions service


SV222 (Failed to connect to Virtualization Extensions '${arg0}' at '${arg1}'.)

SV223 (Connection to Virtualization Extensions '${arg0}' has been restored.)

yes

no

Veeam VMware Collector Service

Veeam VMware Collector: Service status


Service NotRunning

Service Running

yes

no

Veeam VMware Collector Service

Veeam VMware Collector: VMware events have been throttled


VC220 (The internal events queue for the Veeam VMware Collector has reached its limit. vCenter ${arg0} has generated more than the current Collector capacity of ${arg1} events per 30 seconds, therefore some events could be lost. Check for an event storm in vCenter. If a large number of events is a regular situation for your environment, use instructions on changing the event queue size.)

TimerWaitInSeconds: 86400

yes

no