--- title: "Discovery Trigger Events" description: "The following table lists Veeam Virtualization Extensions trigger events and the discovery rules triggered: Example trigger events for topology change (written to the Veeam Collector log on the Collector server) are shown below: When triggered by..." canonical: "https://helpcenter.veeam.com/docs/mp/vmware_guide/discovery_trigger_events.html" breadcrumb: "Veeam MP for VMware User Guides > Appendices > VMware Topology Discovery > Discovery Trigger Events" dateModified: "2026-09-08" --- # Discovery Trigger Events The following table lists *Veeam Virtualization Extensions* trigger events and the discovery rules triggered:

Veeam Virtualization Extensions trigger event (in Veeam Collector log)

Internal Veeam Event ID (seen in event description)

MP discovery rule (script)

Resultant log event in Operations Manager log

Event ID 70 with the New or Changed parameter

SV100

Veeam Stage 1 - Core VMware topology discovery

Event ID 999

Event ID 71 OR

Event ID 70 with the Stage2 parameter

SV101

SV100

Veeam Stage 2 - Host components discovery

Event ID 1010

Event ID 70 with the New or Changed parameter

SV100

Veeam Stage 1 – Virtual Machine Containers discovery

Event ID 1012

Event ID 71 OR

Event ID 70 with the Stage2 parameter

SV101

SV100

Veeam Stage 2 - Virtual Machine discovery

Event ID 1011

Event ID 70 with the Stage2 parameter

SV100

Veeam Stage 2 - Datastore discovery

Event ID 1013
Example trigger events for topology change (written to the *Veeam Collector* log on the Collector server) are shown below:

Event ID

Event Description

70

SV100 New Topology or a host has been added or removed. This event is generated by the Veeam Collector.

This event indicates that the entire infrastructure should be evaluated for possible updates.

71

SV101 Host property or host state has changed on host silver.london.Veeam.org. This event is generated by the Veeam Collector.

One event will be generated for each host that must be re-evaluated.
When triggered by the above events, the discovery script will output events to the *Operations Manager* event log as shown below:

Event ID

Event Description

999

VMwareTopologyDiscoveryCoreObjects.js :
Discovery 'ALL' Complete!
1 API connection(s) discovered;
2 host(s) discovered;
3 datastore container(s) discovered;
1 cluster(s) discovered;
1 datastore cluster(s) discovered;
Script completed in 1.952s

1010

VMwareTopologyDiscoveryHostComponents.js :
TargetComputer = abc.veeam.local
InstallPath = C:\Program Files\Veeam\Veeam Management Pack for System Center\Collector\
Host = esx02.veeam.local
EnableSensorData = true
Script completed in 1.812s

1011

VMwareTopologyDiscoveryVM.js :
TargetComputer = abc.veeam.local
InstallPath = C:\Program Files\Veeam\Veeam Management Pack for System Center\Collector\
Host = veeam07.veeam.local
ContainerId = VMHOST: veeam07.veeam.local:GUESTCONTAINER0
10 Guest(s) discovered.
Script completed in 0.375s

1012

VMwareTopologyDiscoveryVMContainers.js :
TargetComputer = abc.veeam.local
InstallPath = C:\Program Files\Veeam\Veeam Management Pack for System Center\Collector\
3 container(s) discovered.
Script completed in 0.047s

1013

VMwareTopologyDiscoveryDatastore.js :
TargetComputer = abc.veeam.local
InstallPath = C:\Program Files\Veeam\Veeam Management Pack for System Center\Collector\
ContainerId = DATASTORECONTAINER0
22 datastore(s) discovered.
Script completed in 2.656s
The above events indicate successful completion of the Veeam Discovery scripts. Note that the OpsMgr Health Service must have the Proxy setting enabled for the objects inserted by the script to be accepted by OpsMgr. For details see the [Installation Guide](installation_guide.md).