The power of dependencies becomes evident when considering alerts. If you have an
alert configured to trigger when a monitored object is down, you only want that alert
to trigger if a monitored objects is positively down. In other words, you do not want
an down object alert to trigger for an object that is not actually down. Without
dependencies, all monitored objects on a monitored node that is unresponsive to
ICMP queries will also report as down. With dependencies in use, these child objects
will instead display as Unreachable, saving you the hassle of sorting through
numerous false alerts resulting from the failure of a single node to respond promptly
to a status query.
Note: Interfaces may be defined as parent objects, but they cannot be defined as
child objects. SolarWinds NPM determines interface status directly by polling parent
nodes. If the node on which an interface exists goes down, SolarWinds NPM
automatically reports any and all interfaces on that node as unreachable.
n
Creating a New Dependency
n
Editing an Existing Dependency
n
Deleting an Existing Dependency
n
Viewing Alerts on Child Objects
Creating a New Dependency
Creating a new dependency is a straightforward process of selecting the parent and
children objects, as shown in the following procedure.
1. Click Start > All Programs > SolarWinds > Orion Web Console.
2. Click Settings in the top right of the web console, and then click Manage
Dependencies in the Node & Group Management grouping of the Orion
Website Administration page.
3. Click Add new dependency.
185
Creating a New Dependency