Closed Bug 1441559 Opened 7 years ago Closed 5 years ago

Add "user_upgraded" dimension

Categories

(Data Platform and Tools :: General, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: wlach, Unassigned)

Details

Saptarshi suggested we add a dimension that allows us to distinguish errors that occurred immediately after the users upgraded in mission control. mreid helpfully filed an issue there (https://github.com/mozilla/missioncontrol/issues/219), but really this is mostly about adding a dimension to error_aggregates. Not sure exactly how to determine that a user "upgraded" or whether that should mean "just upgraded" or "recently upgraded". Perhaps an example scenario where this distinction was important would be helpful. Saptarshi, do you have any? P.S. documentation for error_aggregates is now here, if it's helpful for context: https://docs.telemetry.mozilla.org/datasets/streaming/error_aggregates/reference.html
Flags: needinfo?(sguha)
for background, my analyses haven't been real time in that i consider new profiles and # of crashes they experience in their first week(e.g. crash rate). For upgraded users, for them too, i consider the first week after upgrade: so in some sense it includes both just and recently upgraded. Since mission control is every five minutes, i think if a version X is released at t0, then we'd see the graph initially represent just upgraded and over time it would be a mix of both leaning towards the recently. I guess for heuristics we could also see 'average time since upgrade' which i guess would slowly increase as time since version release increases. To be honest, i dont know how this will look. Im interested if there are any differences between new users and their crash experience and folks who upgrade.
Flags: needinfo?(sguha)

Moving to General.

Component: Datasets: Error Aggregates → General
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.