1979075 - Glean client_id regeneration in Firefox Desktop

Status: RESOLVED FIXED

(Toolkit :: Telemetry, defect, P1)

Description

[Chris H-C :chutten]

Attachment: Incident doc

Incident doc: https://docs.google.com/document/d/1GfGx2Gw0rWtP0Blu_8cJ9Rxmou5xjn4DJTDThULVsEM/edit?tab=t.0

It appears as though about 6% of Legacy Telemetry clients in the FOG "baseline" ping record report more than one Glean client_id (the one in client_info.client_id). Some are due to the expected nonsense of profile cloning and so forth, but most appear to be due to regeneration: one day they send their final pings from their old client_id and start reporting their first pings from their new client_id.

It's unclear what's going on here.

Comment 1

[Travis Long [:travis_]]

Attachment: Bug 1979075 - Collect Glean data directory info before init.r?chutten

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/f92b009836c0
https://hg.mozilla.org/integration/autoland/rev/c640bfafa636
Collect Glean data directory info before init.r=chutten

Comment 3

[pstanciu]

https://hg.mozilla.org/mozilla-central/rev/c640bfafa636

Comment 4

[Chris H-C :chutten]

The instrumentation we added suggests that there are clients that look like they're regenerating their client_ids who have what appear to be perfectly normal db files (their db.safe.bin are present and have non-zero size, and we're still not seeing any rkv load state errors suggesting corruption). We're going to need more instrumentation deeper in the SDK to dig further.