Triggered Discovery

[BK14]

Hello experts

we are getting thousands of triggered discoveries everyday that uses only a couple of MID servers. They all use the VMWare Probes only as shown in the attached file.

Can you help me find out how and why and what starts these jobs?

Your help is highly appreciated.

 

 

[Maik Skoddow]

Hi @BK14 

When a discovery schedule is set to scan vCenters or ESXi hosts, the process launches VMware-specific probes, such as “VMware - vCenter Datacenters,” which, in turn, launch further probes for ESX machines, virtual machines, clusters, datastores, and networks.

Also check:

• https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0830993 
• https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0813327 

Maik

[BK14]

Hi Maik,

Thank you for the information. These jobs start automatically without any vCenter discovery job running at the time. And out of 60 + Mid servers that we have, these triggered jobs only happen on two MID servers. We have configured all MID servers the same. 

[BK14 · Accepted solution]

I found the issue. It was happening because the events for the vCenter collectors was not set up right. All events were in the list. Removed the unnecessary ones and only kept the ones we need and the triggered jobs went away.