Hello,

We're trying to monitor network services using HTTP sensors and TCP Port Sensors. However, if the device is fully offline, as in not at all available over the network, we've found that the sensors fail to report "Down". Instead they just go into an "unknown" status.

Is there a way to have "Unknown" status actually be "Down" instead?

Article Comments

Dear JohnBobRob,

the Unknown status is set when the sensor gets no data for 2.5 times its scanning interval. It is not possible to configure a sensor to use Down instead of Unknown.

If the device is offline, the request should result in a scan error, setting the sensor down. Please open the sensor settings and check the timeout. If you lower the timeout, do you get the according error message?


Apr, 2018 - Permalink

I've tried using a time out of 30 seconds and 10 Seconds. What I see is that it flaps between a down state and an unknown state. It spends very little time in the down state, most of the time it remains "unknown"


Apr, 2018 - Permalink

Dear JohnBobRob,

what scanning interval do you use for this sensor?


Apr, 2018 - Permalink