Closed Bug 1609482 Opened 1 month ago Closed 1 month ago

Add instrumentation around overflowing the pre-init task queue


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



(Not tracked)



(Reporter: mdroettboom, Assigned: mdroettboom)



(Whiteboard: [telemetry:glean-rs:m11])


(3 files)

To better identify the cause of bug 1609205, it would be useful to know if we are overrunning the pre-init task queue.

Priority: P3 → P1
Assignee: nobody → mdroettboom

Additional requirement: We should report not justif we overflow the queue, but by how many.

Attached file Data review request
Attachment #9121350 - Flags: data-review?(chutten)
Comment on attachment 9121350 [details]
Data review request


    Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate?

Yes. This collection is documented in the Glean SDK's [metrics documentation](

    Is there a control mechanism that allows the user to turn the data collection on and off?

Yes. This collection is controlled by whatever mechanism controls the Glean SDK. For example, in Fenix the UI in the Settings offers this control.

    If the request is for permanent data collection, is there someone who will monitor the data over time?

Yes, Michael Droettboom is responsible.

    Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 1, Technical.

    Is the data collection request for default-on or default-off?

Default on for all channels.

    Does the instrumentation include the addition of any new identifiers?


    Is the data collection covered by the existing Firefox privacy notice?


    Does there need to be a check-in in the future to determine whether to renew the data?

No. This collection is permanent.

Result: datareview+
Attachment #9121350 - Flags: data-review?(chutten) → data-review+
Blocks: 1609734
Blocks: 1609735

(In reply to Michael Droettboom [:mdroettboom] from comment #1)

Additional requirement: We should report not justif we overflow the queue, but by how many.

I really wish we had a way to report these overflows through the error stream (we don't, it would be kind of tricky): we could then just have an error "overflowed_init_metric" and have overflowing metric be reported as errors there

Whiteboard: [telemetry:glean-rs:m?] → [telemetry:glean-rs:m11]
Closed: 1 month ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.