How discovery triggered from vCenter Event Collector selects a MID serverSummaryThis article explains the MID server selection for discoveries that are initiated from the vCenter Event Collector ReleaseAllInstructionsBasically, when vCenter Event Collector is configured, you can specify a MID server to listen for the vCenter events configured in the vCenter Event Collector form. However, this MID server is only used to listen to the changes and pass it on to the instance. 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 system event. Then, if discovery needs to be triggered, the system event will specify which resource do we need to discover and a new directed discovery (only for this resource) is triggered. This discovery is treated like any other discovery in the instance and will therefore use the MID Server selection Algorithm. To Configure the MID server that listens to the vCenter events, you can follow the instructions in our documentation vCenter event collector and configure Capability on the MID server record.To Configure the MID server that is used in the triggered discovery, then you can follow our documentation on MID Server selection and configure the Application and IP range on the MID servers records.