Configure WPM transaction dependencies
You can use the Orion Platform's Dependencies feature to associate objects in a parent-child relationship 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 WPM, 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 following widgets in the Transaction Details and Step Details views to see how their performances are affecting the transaction or an individual step:
- Transaction Application Dependencies
- Transaction Node Dependencies
- Step Application Dependencies
- Step Node Dependencies
You can also set up dependencies to reduce unnecessary alerts from child objects when only the parent object is experiencing problems. For example, if you have 50 devices at a remote site connected to one server, you do 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:
To learn more about managing dependencies, see the Orion Platform Administrator Guide.