Troubleshooting: Dependency Mapping Not Showing Connections Between Monitors

Troubleshooting: Dependency Mapping Not Showing Connections Between Monitors

If the expected connection between source and target monitors is not displayed in Dependency Mapping, follow the steps below to identify and resolve the issue.

Verify Server Credentials (Important)

  1. Dependency Mapping relies on connection data collected (e.g., using netstat) from target servers.
  2. Navigate to Settings → Add/Discover → Discovery → Edit discovery profile.

  1. Ensure that valid server credentials are configured in the discovery profile.
  2. If credentials are invalid or insufficient:
    1. Connection data will NOT be collected,
    2. Dependency mapping will NOT display relationships.

Verify IP Range Configuration

  1. Ensure that the IP address range configured in the discovery profile is sufficient.
  2. Navigate to Settings → Add/Discover → Discovery → Edit discovery profile.

  3. Increase the IP range to include all relevant source and target systems.

Ensure Monitors are Added via Discovery

  1. Confirm that both source and target monitors are successfully discovered.
  2. To verify monitors added via discovery, Navigate to Settings → Add/Discover → Discovery → View Discovered Details.

  4. Monitors should be listed as shown in below screenshot,
  5. If the monitors are added manually,
    1. Create a new Discovery Profile
      1. Ensure:
        1. Proper credentials are configured
        2. Required IP range (including IP address of the existing monitors) includes the target systems
      2. Run discovery for the relevant range.
      3. This process ensures that even existing (manually added) monitors are brought under the Discovery Profile, enabling proper data collection during discovery and allowing dependency relationships to be established.

Validate Discovered Data in Database Tables

  1. Navigate to Settings →  Support → Database Summary → Execute below queries,
    1. SELECT * FROM discovereddevicesinfo;
    2. SELECT * FROM discoveredservicesinfo;
    3. SELECT * FROM admdiscoveryinfo where sourceappid <> -1 and destinationappid <> -1;

  2. From the screenshot, we can confirm that the source and target application monitors are actively communicating. Based on this, the dependency mapping should ideally reflect the relationship between these monitors.
  3. However, if no entries are found in the ADMDISCOVERYINFO table, it indicates that the connection details are not being captured during discovery. Kindly Validate the Netstat information captured during discovery as mentioned below.

Validate Netstat Information

  1. If valid credentials are provided,
    1. Check the netstat information collected,
      1. Navigate to Settings → Support → Logs → Search 'netstatout'.
      2. In netstatout.txt file, Netstat information of each Ipaddress should be displayed.
      3. If the communication was not present in the netstat information, Dependency mapping won't be shown.
      4. Even though connection exists, mapping may not be shown if:
        1. Source and Target monitors are not added via discovery.

Expected Outcome

After performing the above checks, the dependency connections between source and target systems should be reflected correctly in the Dependency Map.
  1. Navigate to Settings → Add/Discover → Discovery → Dependency map. 
  2. After clicking Add New option under Dependency Map, create the Dependency Map by specifying the Dependency Map name, selecting the required servers/applications for mapping and clicking Create.
  3. Before creating the view, You can also choose to view the demo of how the map will be created by clicking the View Demo option.