Closed Bug 1652528 Opened 6 years ago Closed 3 months ago

Allow custom distributions on mobile

Categories

(Data Platform and Tools :: Glean: SDK, task, P1)

task

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: travis_, Assigned: janerik)

References

Details

Attachments

(1 external file)

Proposal for changing an existing or adding a new Glean metric type

Who is the individual/team requesting this change?

Travis Long, Glean SDK team. For Firefox for iOS and possibly other applications.

Is this about changing an existing metric type or creating a new one?

Changing an existing metric

Can you describe the data that needs to be recorded?

Firefox for iOS would like to see the distribution of tabs open from the point of going to background over the course of a day. The metrics ping schedule provides the daily part of this, but we have no way to record multiple counts/numerics in a single metric. If the custom distribution was available (or maybe a new metric type that is more scoped down) then the app could record the number of open tabs when going to background to the custom distribution, and this would be sent on the metrics ping as they requested. This also has the added benefit of providing information for calculating the average tabs open per "session".

Can you provide a raw sample of the data that needs to be recorded (this is in the abstract, and not any particular implementation details about its representation in the payload or the database)

App is opened -> users opens/closes some number of tabs -> app is backgrounded, current open tab count is measured.

What is the business question/use-case that requires the data to be recorded?

How many tabs do users have open on average? What’s the distribution?

How would the data be consumed?

Through Firefox-iOS dashboards.

Why existing metric types are not enough?

Another way to do this would be to create a custom ping and send the current open tab count every time the app goes to background, but this means another table, more metadata that is redundant, more traffic, and makes analysis more difficult because it requires joining additional tables to queries. Existing metric types are not enough because they are not as lean as we could be by allowing custom distributions (or a more tightly scoped version of them).

What is the timeline by which the data needs to be collected?

Q3, 2020

iOS is all that remains, currently

Component: Glean Metric Types → Glean: SDK
Priority: -- → P4
Blocks: 1908760
Assignee: nobody → jrediger
Status: NEW → ASSIGNED
Priority: P4 → P1
Status: ASSIGNED → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: