Unusual detection measures an irrelevant channel

Hi,

The unusual detection can be deactivated globally under Setup > Monitoring > Unusual Detection. Also, it can be disabled/enabled on device-, group-, probe- and root-level under Advanced Network Analysis > Unusual Detection.

Please refer to the links below for further details:
- https://www.paessler.com/manuals/prtg/sensor_states
- https://www.paessler.com/manuals/prtg/monitoring_settings#unusual

Otherwise it's currently not possible to disable the Unusual Detection only on sensor or channel level. You have the opportunity to upvote a Feature Request which you can find here.

Kind regards

Is it possible to create an HTTP/XML sensor without the "Execution time"-channel then? We do not want to disable Unusual Detection for this sensor, even if it was possible. We want the Unusual Detection for the XML-node value we set up the sensor for.

Please have a look at this picture which shows what I'm talking about: https://imgur.com/41IoPMt

The "Value" (which is what I want to monitor) is consistent over the last few months, but the sensor status is showing as unusual because of an unusually high "Execution time", which is not relevant for us to measure.

Thanks in advace.

Hi,

Unfortunately, it's not possible to create the HTTP/XML sensor without the "Execution time"-channel, as this channel is a default channel. You have the opportunity to disable the Unusual Detection via the Settings of the device. You find these setting in the Advanced Network Analysis

Kind regards.

I'm not sure I'm explaining myself clearly. We do want Unusual Detection for the XML-node value we set the sensor up for. Even more importantely, we DEFINITELY want Unusual Detection on other sensors for the same device.

Are you saying that if we do not want Unusual Detection for ONE automatically created (and unwanted) channel for ONE sensor we can, in fact, not use Unusual Detection for any of the 50 sensors we have set up for the same device?

Thanks again.