Applications Systems

SAM Application Dependency polling creates event if node is down

Application Dependency Mapping (ADM) polling triggers an event for "down" nodes instead of skipping them. A message similar to this example appears: ADM polling failed for node WIN-TESTNODE: Request failed - ErrorCode:AgentDeliveryTimeout, Message:'', DetailInfo:2D2816FE for NodeID:2 AgentID:2"

First published date

11/8/2018 2:20 PM

Last published date

12/21/2022 5:29 PM

Overview

Application Dependency polling triggers an event for "down" nodes instead of skipping them. A message similar to this example appears: ADM polling failed for node WIN-TESTNODE: Request failed - ErrorCode:AgentDeliveryTimeout, Message:'', DetailInfo:2D2816FE for NodeID:2 AgentID:2"

Product section

Server Application Monitor

Cause

Application Dependency polling does not currently ignore "down" nodes.

Resolution

Here are two workarounds:

Fix the issue causing the node to be Down.
Disable Application Dependency polling for the node until the issue is fixed, then re-enable polling. There are two ways to disable polling at the node level:
- On the Edit Node page, clear the Application Dependency Mapping Enabled check box.
- Use SolarWinds Query Language (SWQL) to disable polling in the ADM_NodeInventory table.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.