Application Dependency Mapping Deep Dive

shocko

I'm using 2019.04 and monitoring a large windows estate with agents. I run a SWIS script hourly to find nodes without ADM enabled and enable it. So far so good. That said it appears to be picking up dependencies that are not really there i.e. a process on a server A talking to a process/service on Node B is showing on ADM against Node A but it's not really happening.

How does ADM actually work? Is it looking at TCP/UCP stats on the boxes?

sturdyerde

Please be aware that there are suggested limits on how many nodes you enable application dependency mapping (ADM) for. If you have more than this amount, it could conceivably be the reason for your unexpected data. That said, I would open a support ticket to find out for sure.

From the SAM administrator guide: 

Recommended monitoring limits

For optimal performance, use the Application Dependencies feature to monitor up to 500 nodes. Recommended limits per Orion instance for monitoring dependencies include:

Application to application: 500
Application to node: 200
Node to application: 200
Average number of TCP connections per single dependency: 5