How to Address Service Mapping Error "Running process was not found in CMDB, ADM re-run required"

[SN Arch Guy]

I am trying to do a top-down, traffic-based map for an application with type of TCP Endpoint. All traffic and ML system properties look to be set correctly; the respective load balancer and servers all discover without issue; the cmdb_tcp and the cmdb_running_process tables are populated.

I receive the error "Running process was not found in CMDB, ADM re-run required" when running the top-down discovery. Any ideas on how to fix this?

[Rahul Priyadars]

Is Horizontal Discovery was done before running the Top-Down Service Mapping?

See if this KB is of any help for you

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0717161

Regards

RP

[SN Arch Guy · Accepted solution]

this turned out to be an issue where the running processes were transitory and so the top-down discovery could not find them when it ran. the load balancer was directing traffic to a port that was served by initd and then routed to individual processes running on dynamically allocated ports. the pattern was trying to find these processes but could not. we adjusted the pattern to look for other values.

[Jaya5]

Can you share the solution here what u implemented

[SN Arch Guy]

In general, the solution is to update the applicable [custom] pattern to use values other than process/port values. The specifics would depend on your process names, application design, etc.