Some Dpinger / Gateway monitoring clarifications
-
Hello everybody,
I apologize if I’m asking something that has already been answered or if this is the wrong section, but I did some research and I’m still missing some info about dpinger / GW monitoring:
1. When exactly an alert condition is logged (System logs -> gateways)? If I set the the Low Latency Threshold to a very low value (let’s say 20 ms), the gateway status immediately appears as “Warning” in the Status -> Gateways page, but nothing is logged, even after 5/10 minutes. Instead, It seems to me that alerts will start to be logged only after a first “clear” event is triggered (not sure, just a guess)
- These are my understandings of mechanisms involved in the monitoring. Please could you correct them if you find any errors?:
1. Every “probe interval”, an ICMP packet is sent to the target.
2. Every “Alert interval”, an average of all data collected in last “Time period” is calculated. The result is checked against the latency and loss values and actions are taken accordingly.Do you confirm that high thresholds refer to the calculated average over Time Period and not to the single values (single probes)?
And finally, does the "member down" option in the Trigger Level (Gateways groups) mean "high latency AND packet loss"?Thanks a lot for your help!
-
Dpinger results are based on the average of all probes within the time period (default 60 seconds).
Dpinger itself only has one set of thresholds for latency/loss, which are generated from the "high" thresholds in the UI. These are used to determine gateway down types of situations (errors). The warning state is based on the "low" threshold values, and is determined by the higher level logic when it polls for current latency/loss values.
