New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Why will dependent objects not go into paused status automatically when I pause the master object?

Votes:

0

Your Vote:

Up

Down

In my network, I use master objects. For example, I have set a Ping sensor as the master object for a device.

When I pause the master sensor either manually or by schedule, I expect that the dependent sensors are paused, too. Why does this not happen?

dependency hierarchy intention master-object object paused-by-dependencies pausing prtg

Created on Oct 25, 2017 12:06:11 PM by  Martina Wittmann [Paessler Support]

Last change on May 22, 2019 11:31:18 AM by  Maike Behnsen [Paessler Support]



7 Replies

Accepted Answer

Votes:

4

Your Vote:

Up

Down

This article applies to PRTG Network Monitor 19 or later.

How Pausing Works in PRTG

Generally, there are three ways of pausing an object so that it shows a Paused status in PRTG:

  1. By Dependency: If a master sensor is in a Down status, all dependent objects will be paused.
  2. By Intention: You can intentionally pause an object, either
    • Manually or
    • By schedule.
  3. By Hierarchy: You can pause all master and dependent objects by pausing the object that is higher in the object hierarchy.

The Rules in Short

  • Pausing by dependency works for all objects (as far as there are other objects that depend on them). PRTG applies this type of pausing to dependent objects for you in case their master object is in a Down status.
  • Pausing by intention breaks the rule of pausing by dependency. If you pause a master object either manually or by schedule, only the master object is paused. All dependent sensors will further check their status and display it accordingly.
  • Pausing by hierarchy: If you want to pause all objects at a time without pausing every single one, use the object hierarchy relations and pause by hierarchy.

Illustration and Reasons

We will use a Ping sensor that is set as the master sensor for a device as an example.

1. Pausing by Dependency

If a master sensor changes to a Down status, all other dependent objects will be paused. So, monitoring is paused by dependency.

Reason: Because the master sensor (here: master Ping sensor) is primarily responsible for the whole device, its error status triggers the information that the device is down. That is why all other dependent sensors are paused until the device is up again.

Sensors are paused by dependency when the master sensor is down
Click to enlarge.

When the master Ping sensor changes to an Up status again, all other sensors will resume monitoring and show their own states based on the data they retrieve after the re-scan.

If you want to test this, you can simulate an error status in PRTG. It has the same effects. Pausing by dependency works with sensors in a Down (Acknowledged) status as well.

2. Pausing by Intention

You can, of course, pause monitoring intentionally at any time, no matter which sensor status your master sensor currently has.

To pause an object, you have two options:

  1. Pause manually (for example via the context menu), or
  2. Pause by schedule.

If you pause the master sensor manually or by schedule, only the master sensor will be paused, not the other (dependent) sensors on the device. The dependent sensors will show their own status instead.

Reason: If you pause a master sensor, PRTG will get the information that the master sensor stops monitoring, the other sensors on the device need to take over. Therefore, all other sensors on the device will check their status anew and display it.

Pausing a master object by intention
Click to enlarge.

This mechanism is implemented to guarantee maximum monitoring uptime of your network.

3. Pausing by Hierarchy

If you want to pause monitoring for all objects at once, including master and dependent objects, pause the object that is higher in the object hierarchy.

For example, to pause a master Ping sensor and other dependent sensors at a time, pause the whole device.

Pausing objects by hierarchy
Click to enlarge.

More

Created on Oct 25, 2017 1:51:18 PM by  Martina Wittmann [Paessler Support]

Last change on Jul 30, 2019 10:51:02 AM by  Brandy Greger [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello Martina, Hello Maike,

is there any intent to expand these possibilities?

I'm currently reorganizeing our structure to get a better overview and I would find the option usefull to pause a dependend Device via pausing the Master Device with the Masersensor. This should not be the default for sure, but the option to set this via Device or Sensor if needed would be really nice.

Short background: I need to split the Sensors of a Device into two Devices with Different Sensors and the Devices will be located in different groups. I will split the really important sensors from the not so important ones. We are working with Maps a lot and we sadly have some Devices where some unimportant Sensors are constanty going into warningstate, so thats why we will split them up. The Ping Sensor will remain with the important Sensors and it would be nice, in case of Maintanance to only need to pause the "Master" Device and the Device with the unimportant Sensors will be paused as well.

Many thanks in advance.

Created on Jul 8, 2019 5:41:24 PM by  Jacqueline Weigel (11) 2



Votes:

0

Your Vote:

Up

Down

Hi Jacqueline,

to pause a selected device, for example due to maintenance work, you can set up a (one-time) maintenance window via the device's Schedules, Dependencies, and Maintenance Windows settings.

If you want to use the dependency relations of your master sensor, try if Simulate Error Status of your master sensor works out for your intentions.

BR, Martina

Created on Jul 9, 2019 8:03:41 AM by  Martina Wittmann [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Martina,

I'm afraid I did not express myself clearly enough.

If we need to do some maintenance work on our Systems we simply pause them. It is a bit awkward to go to the settings and set the maintenance there just to pause the Devices or Sensors, especially if it isnt clear how long the maintanance work will take.

But that wasnt my Point at all.

Is there a way to pause a Device by pausing another Device?

My first thought was that the dependency settings are the right place for this. And if the Master Sensor is in error state all dependent Devices / Sensors will be paused. But like mentioned above if the Master Sensor is Paused the dependent Devices / Sensors will not be paused.

I dont want you to change your default behavior. I only like to have an option to set an exception via Device or Sensor. So the Device / Sensor will be paused if the Master Sensor is in error state or is paused.

Many thanks in advance.

Created on Jul 9, 2019 1:37:28 PM by  Jacqueline Weigel (11) 2



Votes:

0

Your Vote:

Up

Down

Hi Jacqueline,

Thank you very much for your response.

"Is there a way to pause a Device by pausing another Device?"
No, you will need a sensor to be the determining object to be able to pause another device. I believe that we are speaking from the identical procedure and as we've encountered some issues with recent versions of PRTG speaking about dependencies, please make sure to use the latest available stable version for your purpose.

The procedure would be to define a sensor (let's go with a simple Ping Sensor or use the Green IT sensor).
Afterwards, head over to the desired object (device, group, etc.) that should be paused in case the previously created sensor is 'down'.
Disable the inheritance of 'Schedules, Dependencies, and Maintenance Window' and select an object (in your case the previously created sensor) for 'Dependency Type'.

As soon as the sensor is 'down', the object should be paused by dependency.

Best,
Sebastian

Created on Jul 11, 2019 8:34:19 AM by  Sebastian Kniege [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello Sebastian,

Thank you for your answer.

I'm sorry that I have formulated my question wrong. I know that you need a Sensor to be the determining object.

I also understand that as soon as the determining sensor is 'down', the object that has set the determining sensor for Dependencies should be paused.

And there is no Problem and this all works fine.

I only like to know if there will be the possibility in the future to have the option to decide that not only the 'down' state is responsible to trigger the Dependencies and pause the objects. It would be handy in some cases to define the states for yourself. In my case it would be nice if the Dependencies for some objects would be triggered if the determining sensor is 'paused'.

Many thanks in advance.

Created on Jul 11, 2019 12:39:32 PM by  Jacqueline Weigel (11) 2



Votes:

0

Your Vote:

Up

Down

Hello Jacqueline,

Thank you very much for the clarification. In this case we really spoke about different things.

I believe your request is a legitimate and reasonable inquiry, therefore feel encouraged to raise a feature request as described here:
How Can I Propose New Features Or Sensors For PRTG?

This approach allows other PRTG users and the community to vote for the feature request to strengthen it and to raise awareness for our developers.

Best,
Sebastian

Created on Jul 12, 2019 4:04:47 AM by  Sebastian Kniege [Paessler Support]



Please log in or register to enter your reply.


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.