Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM Documentation > SAM 6.7 Administrator Guide > Monitor application dependencies in SAM

Monitor application dependencies in SAM

Updated: March 14, 2018

The SolarWinds SAM Application Dependencies feature provides a holistic view of application and server connections, expanding monitoring by detecting how applications and nodes interact with each other. You can use data gathered during Application Dependencies polling to:

  • Understand which applications, application processes, and nodes connect with each another.
  • Ensure that the most important data for specific applications is monitored.
  • Identify unmonitored applications and processes that require attention.
  • Leverage latency and packet loss metrics to determine if an issue is caused by an application or the network.

This contextual visibility of relationships between applications and physical/virtual servers also reduces troubleshooting time. For example, instead of searching through many applications, nodes, and component monitors to determine why an application is slow, you can navigate to the Incoming Connections resource and analyze application dependencies to pinpoint the source of the issue.

The Incoming Connections resource on the Application Details and Node Details pages displays data gathered about application dependencies, as shown in this example:

ADMIncomingConnections_513x331.png

SAM uses two types of polling to discover and monitor connections the following types of connections:

ADM_application_to_application_438x40.png

ADM_node_to_application_441x39.png

ADM_application_to_node_442x39.png

  • Application to application, in a typical client/server process monitored by SAM
  • Application to node, with a server process not currently monitored by SAM
  • Node to application, with a client application process not monitored by SAM

To provide a more granular picture of application dependencies, the Connection Details page shows processes and ports for connections, plus node, application, and process status. You can also enable polling to display latency and packet loss statistics. The Connection Details page shows the entire communication stack from one node to another, which makes it a unique troubleshooting tool.

ADM_ConnectionDetailspage_570x261.png

Application Dependencies polling overview

SAM uses two types of polling to collect application dependency data:

Application Dependency polling is enabled by default but Connection Quality polling is not. See Enable Connection Quality polling.

  • Application Dependency polling: Discovers and monitors the following types of connections:
    • Application to application, in a typical client/server process monitored by SAM
    • Application to node, with a server process not currently monitored by SAM
    • Node to application, with a client application process not monitored by SAM
  • Connection Quality polling: Tracks TCP communication traveling from client nodes hosting applications to target nodes. This synthetic polling collects latency and packet loss statistics for connections without intercepting network traffic, also known as "packet sniffing."

How SAM uses Orion agents to find and monitor application dependencies

SAM uses Orion agents to flag nodes for Application Dependency polling. An agent must exist on at least one of the two nodes for which you want to display dependencies. If a node does not host an agent, the Incoming Connections resource displays sample data, as shown here.

ADM_IncomingConnections_SampleData_515x305.png

Agent plug-in overview

The Orion Platform deploys and removes agent plug-ins as you enable and disable features in the Orion Web Console. A single agent-managed node may include multiple plug-ins to handle different tasks such as polling.

To support the Application Dependencies feature, SAM deploys agent plug-ins to nodes to monitor connections and network communications, then displays data on the Incoming Connections resource and Connection Details page.

To avoid having to update agent-plug-ins manually, make sure the Allow Automatic Agent Updates option is enabled on the Agent Settings page.

For Application Dependency polling:

SAM does not deploy Application Dependencies plug-ins to the Main Polling Engine (that is, the Orion server) to avoid performance issues due to the number of connections that may be involved.

  • SAM deploys plug-ins to nodes if Application Dependency polling detects application-to-application or application-to-node connections.
  • Agent plug-ins collect data about dependencies between applications (application-to-application connections) and/or nodes (application-to-node connections). It is available in Linux x64, Linux x86, and Windows versions.

For Connection Quality polling, if enabled:

  • SAM deploys additional agent plug-ins to collect TCP latency and packet loss metrics.
  • For Windows nodes connected to clients that host applications and application processes, the TCP agent plug-in includes an Npcap driver to support Nping.

If you enable Connection Quality polling and disable it later, SAM removes the TCP agent plug-in but not the Npcap driver. See Remove an Npcap driver after disabling Connection Quality Polling in the SolarWinds Success Center.

If polling fails for Windows Server 2012 nodes, see Agent-related issues.

SAM relies on server-initiated communications to detect "from” or to" nodes, also called “passive agents” or “agentless" nodes. Only one node in a pair requires an agent plug-in. However, note that the type of data gathered by polling depends on communication settings for both nodes, as described here:

  • If target and client nodes both host agent plug-ins, SAM collects data via Application Dependency and Connection Quality polling for both nodes.
  • If only the target node has an agent plug-in, SAM collects IP address and port data for the client node but not application details, process names, or connection statistics.
  • If only the client node has an agent plug-in, SAM collects IP address and port data for the server node. If Connection Quality polling is enabled and SAM deployed an TCP agent plug-in to the connection source node, polling can capture latency and packet loss statistics.

Use the Manage Agents page to check the status of agent plug-ins.

To get started with monitoring connections between applications and nodes, see Configure the Application Dependencies feature. Additional topics related to application dependencies include:

 
Last modified

Tags

Classifications

Public