Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Network Performance Monitor (NPM) > Polling Interval of the Parent node, Parent-child dependencies, and custom properties for Dependency alerts

Polling Interval of the Parent node, Parent-child dependencies, and custom properties for Dependency alerts

Table of contents
Created by Jane Baylon, last modified by MindTouch Content Copy on Nov 13, 2015

Views: 34 Votes: 2 Revisions: 6

Overview

This article details the Polling Interval of the Parent node, Parent-child dependencies, and custom properties of Dependency alerts.

Environment

All NPM versions

Detail

In creating a dependency, SolarWinds recommends to adjust the Polling Interval of the Parent node. This is because when the child nodes are detected "down", it triggers an alert without detecting the parent node first.

 

To reduce the Node Status Polling time by half (for example, from 240 to 120 seconds), go to the Orion Web Console> Settings> Manage Node> Select the Parent Node> Edit Properties> Node Status Polling, and then create a new dependency.

 

To set up an alert set up for Parent-Child dependencies without notifying all members are "down", SolarWinds recommends to use an AND – OR type of trigger conditions and specify all the name of the individual devices. For example,
Type of Property to Monitor: Group Member
Trigger Alert when all of the following apply
---Member Status is equal to down
---Trigger Alert when any of the following apply
-----Member Name is equal to cisco-asr-500
-----Member Name is equal to juniper-sw2300
-----Member Name is equal to tok-vvrt-1sam


The key factor for an “AND” and “OR” conditions are the indentations of the alert conditions. An alternative way is to create a Custom Property and specify all the nodes on that site. 


After creating a custom property, set up an Advanced Alert and select the custom property you have created. For example,  
Type of Property to monitor: Node
Trigger Alert when all of the following apply
---Node is equal to down
---Site is equal to Other Equipment


Note: “Site” is the name of the custom property and “Other Equipment” is where the devices are included.

 

Last modified
13:53, 13 Nov 2015

Tags

Classifications

Public