What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

Configure dependency through multi-edit feature?



Hello team,

I cannot configure dependency through the multi-edit feature. What I do is the following:

  1. Enter a device.
  2. Select all sensors (except Ping)
  3. Click configuration (from the multi-edit menu)
  4. Dependency option does not have the option to define an object.

I wanted to select all my sensors and set them to depen on ping sensor for this device, however, it seems like it is only working when configuring sensors one by one. Is that correct?

Thank you.

dependencies dependency dependency-on-ping multi-edit

Created on Feb 3, 2014 3:00:37 PM

Last change on Jun 22, 2015 2:02:36 PM by  Luciano Lingnau [Paessler]

5 Replies




thank you very much for your KB-Post. Setting dependencies via the Multi-Edit is not possible, this is correct. It's actually intended, to avoid the creation of dependency loops, with never awaking devices & sensors (which can easily happen by accident).
The key here for this would be going into the Settings of the Ping Sensor, and set it to be the Master for parent object under Dependencies. This will cause the Ping Sensor to pause all other sensors on the device, if itself fails.

best regards.

Created on Feb 4, 2014 11:44:01 AM by  Torsten Lindner [Paessler Support]



Oooh, great!!! Thank you very much

Created on Feb 4, 2014 1:44:02 PM



So if you do make the PING sensor the Master for parent object for a device (say a switch), how then can you then make that switch dependent on an upstream router, for example?

This is problem I am currently having with our vast network... I am struggling to set the dependencies correctly to reflect real world dependencies.



Created on Sep 24, 2014 2:10:19 PM



The important thing is to make the sensors and devices dependent on the "main Ping Sensor". You can also work with sub-groups/cascading groups here, to make entire groups depending on a Ping Sensor (of the Router). So here, create a group with all servers, etc. that are actually "behind" this router, and then make this sub-group dependent on the Ping-Sensor of the router. And then keep the device-dependencies on the "Server-device" and "Print-Device" that each of their own Ping-Sensor will be the master object for this device and then pause all sensors on the server, if only the server is down. It may also help, to look into the Notification Summarization Settings which summarize several notifications, if they occur within a certain time limit.

Created on Sep 24, 2014 2:54:53 PM by  Torsten Lindner [Paessler Support]



OK I think I follow what you are saying here... thanks for the explanation. It's too bad this dependency design methodology isn't documented in the manual.

Thanks again.

Created on Sep 24, 2014 3:16:43 PM

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.