Hi,

Defining the number of pings required to fail before a Ping Sensor is maked as down is easily done by modifying parameter: "Ping Count".

The problem I have is with defining the number of successful pings required to mark the Sensor as Up again after it has been down. It marks it UP only after 1 successful ping. I don't see any parameter related to this and it produces our company great grief when a circuit comes back briefly for a second or two many times per hour. It generates an endless number of Notifications that soon overwhelm any support desk. Isn't there a way I can set a parameter to only mark a sensor Up when X number of Successful Pings are received?

Thanks,

Article Comments

Hello,

I am afraid that the only option would be to turn off the notifications that are sent out when condition clears.

Best regards


Apr, 2016 - Permalink

I am very surprised by this limitation. We come from a Nagios background and with that platform the 'check_ping' command can be fine tuned to anything we want. For example you can tell it to send 10 pings and only mark the host as UP if 7 of them get positive response. Marking a host as UP when a single ping gets responded to is not an accurate representation of true conditions.


Apr, 2016 - Permalink

Hello,

You can try the following workaround: in the sensor settings, please set "Ping Count" to e.g. 10. Then in the channel settings of the sensor channel "Packet Loss", please enable limits and set "Upper Error Limit" to e.g. 50%, so the sensor will go into error state if packet loss is above this limit.


Apr, 2016 - Permalink

Thanks Isidora. I just tested your solution and it works perfectly. At 50% the sensor will not be marked as UP until at least 51% of the pings are successful.


Apr, 2016 - Permalink