zenping and device polling frequency

Interested in confirming the actual ping status process with ZenOSS.

Reading the admin guide has led to confusion, so I may have missed where it is explicitly mentioned.

Is ZenOSS doing 4 sequential checks 1min apart, on a 10min cycle??

Other toolsets ping x seconds, then after first failure, reduce time by 50% and after the 3rd failed, flag the node as down (eg: around 1m45s of failures after initial ping)

We have not done any modifications to /opt/zenoss/etc/zenping.conf

We only have 1 zenping instance.

Or Networks team is questioning our response time to alert for node down compared to what we are moving away from. Here is an example of the polling inconsistencies from a device perspective...

.

Nov  7 06:49:46.906: ICMP: echo reply sent, src 192.168.24.74, dst 192.168.244.28, topology BASE, dscp 0 topoid 0

Nov  7 06:50:39.180: ICMP: echo reply sent, src 192.168.24.74, dst 192.168.244.28, topology BASE, dscp 0 topoid 0

Nov  7 06:50:46.878: ICMP: echo reply sent, src 192.168.24.74, dst 192.168.244.28, topology BASE, dscp 0 topoid 0

Nov  7 06:51:39.166: ICMP: echo reply sent, src 192.168.24.74, dst 192.168.244.28, topology BASE, dscp 0 topoid 0

Nov  7 06:53:00.026: ICMP: echo reply sent, src 192.168.24.74, dst 192.168.244.28, topology BASE, dscp 0 topoid 0

Nov  7 06:59:39.903: ICMP: echo reply sent, src 192.168.24.74, dst 192.168.244.28, topology BASE, dscp 0 topoid 0

Nov  7 07:00:39.208: ICMP: echo reply sent, src 192.168.24.74, dst 192.168.244.28, topology BASE, dscp 0 topoid 0

Nov  7 07:00:46.841: ICMP: echo reply sent, src 192.168.24.74, dst 192.168.244.28, topology BASE, dscp 0 topoid 0

Nov  7 07:01:39.201: ICMP: echo reply sent, src 192.168.24.74, dst 192.168.244.28, topology BASE, dscp 0 topoid 0

Nov  7 07:01:46.627: ICMP: echo reply sent, src 192.168.24.74, dst 192.168.244.28, topology BASE, dscp 0 topoid 0

Nov  7 07:02:39.217: ICMP: echo reply sent, src 192.168.24.74, dst 192.168.244.28, topology BASE, dscp 0 topoid 0

 Thanks in advance.