Which Semaphores are used during Discovery process (Horizontal and Cloud Discovery)

[varunkumar11863]

Hi, I am trying to understand the platform impact for creating new schedules. We have different semaphores based on the Tasks like API_INT, AMB_SEND, DEFAULT, etc.

My query is, which semaphore is used during Discovery process (Horizontal and Cloud Discovery)? I see that sensors are processed via worker thread using Async Job, but MID has to poll ECC. Does it use API_INT? If yes, I am not able to see the semaphore usage in stats.do as API_INT always has max available semaphore.

[Abhishek_Thakur]

Hello @varunkumar11863 ,

These are the below semaphores used during the discovery: -

1. Mid Server Semaphores

• MID_Discovery: Used to manage the maximum number of concurrent Discovery jobs that a MID Server can handle.
• MID_Discovery_Queue: Ensures proper queuing of discovery probes sent to the MID Server.
• MID_Orchestration: If Orchestration is involved, this semaphore regulates the orchestration activities.

2. Probe Semaphores

• ECCQueue: Manages the ECC (External Communication Channel) queue to control the flow of data between the instance and the MID Server.
• Discovery.DeviceHistory: Prevents duplicate or redundant scans of devices during Discovery.

3. IP Range Semaphores

• Discovery.IPScan: Controls the scanning of IP ranges, ensuring the same IP is not scanned by multiple Discovery jobs simultaneously.

4. Pattern Execution Semaphores

• Discovery.Pattern: Regulates the execution of Discovery patterns, ensuring controlled pattern-based scanning.

5. Cloud Discovery Semaphores (if applicable)

• Discovery.Cloud: Used during cloud infrastructure discovery to manage API calls and concurrency limits.

Please mark my answer as accepted solution and give thumbs up, if it helps you.

Regards,

Abhishek Thakur