Bugzilla

Details of this bug are available in this document:

https://docs.google.com/document/d/1J-KM7wFuJkWMHwib9Is-Ymu58-pkQvPgHnOtwr1hcvU/edit

Analysis is ongoing here:

https://iodide.telemetry.mozilla.org/notebooks/350/

We are proposing adding a new metric to count the number of baseline pings during the lifetime of each metrics ping.  This would be a counter in the metrics ping that is incremented every time a baseline ping is collected, and reset every time a metrics ping is sent (has ping lifetime).

This will be helpful in determining where in the code the problem may lie.  Are we sending baseline pings that don't arrive at the endpoint, or is the metrics ping truly being sent without any intervening baseline pings?

Details of this bug are available in this document:

https://docs.google.com/document/d/1J-KM7wFuJkWMHwib9Is-Ymu58-pkQvPgHnOtwr1hcvU/edit

Analysis is ongoing here:

https://iodide.telemetry.mozilla.org/notebooks/350/

We are proposing adding two new metrics:
- to count the number of baseline pings during the lifetime of each metrics ping.  This would be a counter in the metrics ping that is incremented every time a baseline ping is collected, and reset every time a metrics ping is sent (has ping lifetime).
- the inverse: to count the number of metrics pings during the lifetime of each baseline ping.  This would be a counter in the baseline ping that is incremented every time a metrics ping is collected, and reset every time a baseline ping is sent (has ping lifetime).

This will be helpful in determining where in the code the problem may lie.  Are we sending baseline pings that don't arrive at the endpoint, or is the metrics ping truly being sent without any intervening baseline pings?