ITOM Visibility | How To Identify if a Discovery Pattern Failed Due to a Stopped or Bounced Running ProcessSummaryWhen the Application Dependency Mapping probe Discovers a Running Process that triggers an Application type Horizontal Discovery Pattern, sometimes the Running Process that ADM detected can stop or bounce before the Pattern executes and runs Process Detection.This can result in a pattern failure if the Pattern depends on data from the running process to use in conditions or to create variables used by the pattern in later steps.Error Messages in Payload Processing section of the Discovery Log are usually not indicative that the root cause is due to the Running Process having stopped or bounced.In this case we can quickly check the Process Detection section of the Pattern Log to verify whether the Running Process stopped or bounced. Definitions • PID Process ID (PID) is a unique numerical identifier assigned to each running process on a host/server. • Stopped PID The Running Process that the ADM Probe Discovered is no longer running on the host/server. • Bounced PID The Running Process that the ADM Probe Discovered restarted and has been assigned a different PID on the host/server.ReleaseAll ReleasesInstructions1. Open the Horizontal Discovery Log record. 2. Select Process Detection at the top of the left-hand column to see more information about it in the right-hand column • Note: If the Discovery Log has 2 Process Detection sections then select the first one from the top. 3. In the right-hand column look for the result of the first command that was run in the Process Detection section. • On Unix/Linux Hosts the command will be similar to below: Executing SSH command: ps -eo user,pid,ppid,comm,args | grep -I <running_process_pid> | grep -v grep • On Windows Hosts the command will be similar to below: Executing WMI query on host: <ip_address_of_host> with namespace: root/cimv2 and query: Select * From Win32_Process WHERE (ProcessId = <running_process_pid>) 4. Go to the next line in the Discovery Log for the Command result. 5. If the Command result is null/empty then the Running Process has stopped or bounced. • Command result: