Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Web Performance Monitor (WPM) > Web Performance Monitor Administrator Guide > Transactions > Transactions and dependencies

Transactions and dependencies

Table of contents
No headers

The SolarWinds Orion Manage Dependencies feature enables you to associate objects in a parent-child relations that shows one object has a dependency on another. WPM lets you set dependencies on transaction steps as well as transactions, providing you with an increased level of granularity to isolate dependencies at the level of single browser actions.

For the purposes of Web Performance Monitoring, dependencies are useful in conjunction with NPM and SAM for tying nodes and applications to transactions and transaction steps to facilitate troubleshooting. This means that you can view the status of nodes and applications associated with a transaction or transaction step using the Transaction Application Dependencies, Transaction Node Dependencies, Step Application Dependencies and Step Node Dependencies resources in the Transaction Details and Step Details views to see how their performances are affecting the transaction or an individual step.

Setting up dependencies can also be for avoiding unnecessary alerts from child objects when only the parent object is actually experiencing problems. For example, if you had 50 devices at a remote site connected to one server, you would not want to be swamped with 50 alert messages from these if the server went down. By specifying that each device is dependent on the server, these devices would be shown as Unreachable if the parent server went down, and any alerts triggered by Down status would therefore be suppressed for these devices.

There are two ways to set up dependencies:

Last modified
15:11, 18 Jul 2016

Tags

Classifications

Public