Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > SAM Application Dependency polling creates event if node is down

SAM Application Dependency polling creates event if node is down

Updated February 9, 2018

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"

Environment

  • SAM 6.6

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. 
 
Last modified

Tags

Classifications

Public