1368579 - Consider aggressive culling of persisted telemetry in "low storage" situations

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: Metrics, enhancement)

Description

[:Grisha Kruglov]

This bug exists as a follow-up to Sync Ping work, which makes heavier use of local persistence than was the case prior with Java Telemetry. As opposed to the core ping, which is treated as "upload right away", sync pings are bundled out of telemetry information aggregated over some time, which is persisted in a special "local ping" json-backed store. As such, it becomes theoretically possible under certain circumstances to amass a large amount of local telemetry data which, for whatever reason, we're failing to bundle into a Sync Ping and upload.

We already have "culling" implemented for JSON-backed ping stores (keep at most 40 non-uploaded pings). A reasonable approach here would be to introduce a concept of "aggressive culling", and tightly define circumstances under which it may occur as well as the trade-offs being made.

Comment 1

[Nevin Chen(Not active on Bugzilla)]

Hi Grisha
May I know are you working on this?
Can I mark this P2?

Comment 2

[BMO Automation]

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.