Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Network Performance Monitor Getting Started Guide > Reduce alerting noise > Define object dependencies in SolarWinds NPM

Define object dependencies in SolarWinds NPM

Table of contents
No headers
Created by Chris.Moyer, last modified by Chris.Moyer on Oct 04, 2016

Views: 133 Votes: 0 Revisions: 10

On your network, there are objects that are dependent on other devices to function. For example, all monitored objects behind an edge router are dependent on that router for connectivity. If the router has problems or goes down, any dependent devices will also appear to have problems, and you will receive status alerts about those devices as well.

However, if you define those nodes as being dependent on the edge router, you will not get false alerts about the status of dependent nodes when the parent object has issues.

When you use dependencies, consider the following:

  • Dependencies themselves do not prevent alerts from being triggered. Instead, dependencies prevent the child objects from going down, and as a result, down node alerts are not triggered. By using dependencies, status alerts are prevented from triggering, but all other alerts are triggered.
  • A child object can have several parents, and the child's status only turns to Unreachable if all parents in all defined dependencies go down.

In this example, you will create a dependency between a router and all the devices monitored by an IT department. This dependency can be used to limit an alert, which is then triggered only for the router that goes down, and not when a monitored device is unreachable because the router is down.

  1. Click Settings > All Settings in the menu bar.
  2. In the Node & Group Management grouping, click Manage Dependencies.
  3. Click Add New Dependency.

    File:Success_Center/New_Articles/NPM-CHM-Import/Onboarding-Guide-CHM/0F0/080/Dependency_AddNew.png

  4. Select the parent object or group, and click Next.

    File:Success_Center/New_Articles/NPM-CHM-Import/Onboarding-Guide-CHM/0F0/080/Dependency_SelectParent.png

  5. Type a Dependency Name, select the child entities, and click Next.

    File:Success_Center/New_Articles/NPM-CHM-Import/Onboarding-Guide-CHM/0F0/080/Dependency_AddChild.png

  6. Review the settings for the dependency. If there are active alerts on child objects, they are listed on this view.
  7. Click Submit.

The dependency appears on the Manage Dependencies page.

You can also display the dependency on custom views in the Orion Web Console.

Last modified
09:39, 4 Oct 2016

Tags

Classifications

Public