Looking at a FFTV ingestigation of core pings, the sequence number for core pings seem to not have gaps when crashes happen, but would be missing pings. That means that `seq` for the baseline ping does not match the count of observed foreground sessions. This has impact on critical metrics, where we might see lower numbers for e.g. Can we make the baseline ping more resilient for crashes or other uncontrollable termination events? I see that we added ping lifetime metrics persistence in bug 1505732, but does that solve the issue here?
Bug 1536930 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Looking at an ingestigation for FFTV of core pings (from the *old* Telemetry library), the sequence number for core pings seem to not have gaps when crashes happen, but would be missing pings. That means that `seq` for the baseline ping does not match the count of observed foreground sessions. This has impact on critical metrics, where we might see lower numbers for e.g. Can we make the baseline ping more resilient for crashes or other uncontrollable termination events? I see that we added ping lifetime metrics persistence in bug 1505732, but does that solve the issue here?