Closed Bug 1907227 Opened 5 months ago Closed 5 months ago

Add telemetry probe for Rust ingest times

Categories

(Firefox :: Address Bar, task, P1)

task

Tracking

()

RESOLVED FIXED
130 Branch
Tracking Status
firefox130 --- fixed

People

(Reporter: adw, Assigned: adw)

References

Details

(Whiteboard: [sng])

Attachments

(2 files)

Add a telemetry probe that counts how long each ingest takes in the Firefox Suggest Rust component.

Blocks: 1900496

This adds a new Glean timing distribution called quick_suggest_ingest_time to
the urlbar namespace. The distribution is updated on each successful ingest. I
don't think it makes sense to record failed ingests because they would likely
skew the data.

Attached file request.md

Data review request for the new urlbar.quick_suggest_ingest_time timing distribution

Attachment #9412168 - Flags: data-review?(chutten)

Comment on attachment 9412168 [details]
request.md

Actually, there's a new Data Review process in town. Starting May 7, all data collections in projects reviewed in Phabricator also perform data review in Phabricator: https://wiki.mozilla.org/Data_Collection#Firefox_Desktop.2C_Firefox_and_Focus_for_Android.2C_Gecko_.28from_May_7.2C_2024.29

In short, following what the Herald message says, code authors and code reviewers together determine what level of review is needed for new or expanded data collections. You might never need to fill out a data review request form again! (For instrumentation in projects reviewed in Phabricator, anyway)

Attachment #9412168 - Flags: data-review?(chutten)
Pushed by dwillcoxon@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f2788727ae77 Add telemetry probe for Rust ingest times. r=daisuke,urlbar-reviewers
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → 130 Branch

Bug 1907696 changed the frequency that this telemetry will be recorded with, and also the expected values. Before that bug, this telemetry measured ingest of all suggestion types combined. So during ingest, it would be recorded only once, and the time that was recorded measured the total ingest of all suggestion types combined. After that bug, this telemetry measures ingest of each individual suggestion type. So during ingest, it will be recorded as many times are there are enabled suggestion types, and each recorded value will be smaller because it measures the time for only one individual suggestion type. So for example if Fakespot, Yelp, MDN, AMO, AMP, and Wikipedia are enabled, it will be recorded 6 times per ingest.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: