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

[OPEN] Change/Alter Business Process Sensor behavior for Paused Child sensors

Votes:

14

Want this feature implemented, too? Please upvote by clicking Thumbs up!

(Posts as a reply won't be published in this feature request thread. Read Me!)

User story

When a child object/sensor of a business process sensor is in a paused state, it moves the business process sensor into a down state, although there may be valid reason for the child sensor to be in a paused state, perhaps for some kind of scheduled maintenance. It would be nice if this either didn't escalate the business process to a down state, or how it treated a paused sensor was configurable inside of the business process settings.

Acceptance criteria

  • Provide an option to configure behavior of sensor in paused state

Status

Open

business-process down improve-prtg paused prtg-kbtracker

Created on Dec 10, 2018 10:42:01 PM

Last change on Aug 6, 2021 11:48:55 AM by Florian Lesage [Paessler Support]



3 Replies

Votes:

1

I agree with Jake that the BPS needs to behave the same as other sensors in regards to a paused state would indicate an unknown status. I'm at a loss as to why this is the behavior. It makes reporting with the BPS very difficult.

Thoughts?

Benjamin Day
Paessler Support

Created on Dec 11, 2018 8:47:19 PM by Benjamin Day [Paessler Support] (1,441) ●2 ●1



Votes:

1

More valid reasons are stated for example in https://kb.paessler.com/en/topic/69862-paused-sensors-in-business-process-sensor

Created on Jul 1, 2019 10:23:56 AM



Votes:

1

We're just facing the same Problem. The normal behavior of PRTG for a (manually) paused sensor would be: "ignore this sensor until it's resumed".

Therefore the proposal which Benjamin Day made would be a good solution. The Business-Prozess Sensor should go in a "unknown" status in such a situation.

Another alternative would be to let the user decide (on sensor creation / settings) how paused sensor's should be handled.

Created on Jan 3, 2020 3:25:39 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.