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

Article Comments

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


Dec, 2018 - Permalink

More valid reasons are stated for example in https://helpdesk.paessler.com/en/support/solutions/articles/69862-paused-sensors-in-business-process-sensor


Jul, 2019 - Permalink

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.


Jan, 2020 - Permalink