Triggered Discovery

BK14 · ‎07-18-2025

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.

BK14 · 3 weeks ago

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.

View solution in original post

Shubham_Jain · ‎07-18-2025

@BK14 Can you verify the Discovery Log based on Device ID or Discovery Status to see more details?

✔️ If this solves your issue, please mark it as Correct.

✔️ If you found it helpful, please mark it as Helpful.

—
Shubham Jain

BK14 · ‎07-21-2025

Hi Shubham,

I don't see anything in the log section, just Discovery Started and Stopped.

In ECC I see these probes:

2025-07-21 09:56:06 VMWareProbe VMWarevCenterClusterDRSProbe input

2025-07-21 09:56:06 VMWareProbe VMWarevCenterVMNICsProbe input

2025-07-21 09:56:04 VMWareProbe VMWarevCenterVMsProbe input

2025-07-21 09:56:06 VMWareProbe VMWarevCenterVMTagsProbe input

The job takes a few seconds to finish.

BK14 · 3 weeks ago

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.