Application dependency mapping (ADM) creates upstream and downstream relationships based on TCP connections?

[Torb]

In the sales presentation it says "Application dependency mapping (ADM) creates upstream and downstream relationships between interdependent applications by identifying which devices are communicating with one another, which TCP ports they are communicating on, and which processes are running on these devices"

When I run discovery I see that the Netstat list is populated on the scanned servers, but I don't see any relationships between  servers in the "Dependency view" based on network traffic. I can see VMware host and network switches and all that basic Infrastructure stuff in the view, but not that for exampel Webserver01 is upstream to SQL01 because SNOW is seeing port 1443 connections between the two. 

Is there some filter or special view I must select to see this?

[adilrathore]

What I new is that the Active processes probe of ADM will gather all the Active running processes and feed this data to the Process classifiers: These process classifiers will create the applications records and the relationships whether upstream or downstream.

I would also be eager to know how Active connections probe would create connections.

[Torb]

Are you seeing these Upstream/downstream relationships in the dependency view?

[Ashutosh Munot1]

Hi,

ADM will stored data in running process table and then depending upon the process other patterns and probes will be triggered i.e. MSSQL DB , IIS, Tomcat,vmware,etc.

Then it will create relationship with Server and this application and files but not will running process.

Thanks,
Ashutosh

[Torb · Accepted solution]

I found the answer myself. Not sure why this is so undocumented.

So first thing, first. Discovery comes with ~60 predefined Process classifications. When you have a "Process classification" ServiceNow automatically creates a relationship between servers based on the TCP connections for that "process classification". This list of TCP connections are discovered during Discovery (netstat).

To prevent noise (I assume), Discovery won't map everything. So if you have a Webapplication talking to a SQL server, but it's not communicating directly through IIS or Apache (that are out of the box "Process classifications") , the connection will not be mapped.

To create a relationship all you have to do is create a new "Process Classification" with the process name that is doing the TCP connection. This information can easily be found in the "TCP connection" table on the server in question.

To find the list of "process classifications" or to create a new go to "Processes" under "Discovery definition"

Some examples.