Hi Andreas,Thank you for showing interest and looking into this case.Here attached is a non-exhaustive list of the probes and corresponding time vicinity where missing happens for built-in ping toward b-root (mom id 1010).Hope it could be useful.Regards,wenqinprobe_id;left_tstp;right_tstp
Hi Wenqin,
that was a weird case where specific probe has time synchronization issues.
We saw a lot of debug messages in our raw logs coming from probe
complaining about time sync issues.
If you have more examples including other probes please send us details
and we will happily check it for
On 2016-09-02 12:20, Wenqin SHAO wrote:
> Thanks for confirming. The specified frequency is indeed well respected. When
> there is no data-missing, the interval shift rarely exceed 14s, small
> compared to 240s the scheduled interval.
> What intrigues me is that the exact phase/timing is as well
> 2. As observed by @Robert, most ‘abnormal’ interval is actually very close
> to integer times of planned value.
> If I get your message right, you are indicating that planned measurements
> can be skipped for the reasons you mentioned and shall kick-off again
> following the previous timing,
On 2016-09-01 19:14, Wenqin SHAO wrote:
> 1470055259
> 1470055499
> 1470055978
> 1470056216
>
> Four measurements are retrieved within the given time range. I noticed that
> time interval between the 2nd and the 3rd measurement is 479s much larger
> than the planned value 240s.
> How come?
479
Hi Wenqin,
It may be because the probe is busy doing other things. We noticed a high
interval between the scheduling and the actual measurement of one-off
measurements on busy probes in
http://conferences.sigcomm.org/imc/2015/papers/p437.pdf
