Thunderbird Glean migrations
Categories
(Thunderbird :: General, task)
Tracking
(thunderbird_esr115 wontfix, thunderbird_esr128 affected)
People
(Reporter: mkmelin, Assigned: mkmelin)
References
(Blocks 2 open bugs)
Details
Attachments
(26 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
Bug 1899602 - migrate tb.account.size_on_disk and tb.account.total_messages to glean. r=freaktechnik
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
Bug to track the actual migration of Telemetry probes to Glean.
Assignee | ||
Comment 1•5 months ago
|
||
Assignee | ||
Comment 2•5 months ago
|
||
See https://firefox-source-docs.mozilla.org/toolkit/components/glean/user/migration.html#discrete-distributions-kind-categorical-enumerated-or-boolean-use-glean-s-labeled-counter
I think the existing probe was wrong. It collected integers but labels were expected.
Assignee | ||
Comment 3•5 months ago
|
||
Assignee | ||
Comment 4•5 months ago
|
||
Assignee | ||
Comment 5•5 months ago
|
||
Apparently this was not tested before.
Assignee | ||
Comment 6•5 months ago
|
||
Assignee | ||
Comment 7•5 months ago
|
||
Assignee | ||
Comment 8•5 months ago
|
||
Assignee | ||
Comment 9•5 months ago
|
||
Assignee | ||
Comment 10•5 months ago
|
||
Assignee | ||
Comment 11•5 months ago
|
||
Assignee | ||
Comment 12•5 months ago
|
||
Assignee | ||
Comment 13•5 months ago
|
||
Assignee | ||
Comment 14•5 months ago
|
||
Assignee | ||
Comment 15•5 months ago
|
||
Assignee | ||
Comment 16•5 months ago
|
||
Assignee | ||
Comment 17•5 months ago
|
||
Assignee | ||
Comment 18•5 months ago
|
||
Assignee | ||
Comment 19•5 months ago
|
||
Assignee | ||
Comment 20•5 months ago
|
||
Assignee | ||
Comment 21•5 months ago
|
||
Assignee | ||
Comment 22•5 months ago
|
||
Assignee | ||
Comment 23•5 months ago
|
||
Assignee | ||
Comment 24•5 months ago
|
||
Assignee | ||
Comment 25•5 months ago
|
||
:Dexter, :chutten - would be grateful for any feedback on these migrations
Comment 26•5 months ago
|
||
Wow, that's 23 reviews. Any in particular you'd consider an exemplar of the whole set, or would you like eyes on all of them?
Assignee | ||
Comment 27•5 months ago
|
||
The most prominent classes are likely these:
We have a fair amount of labeled quantities (which isn't a type). I've used type: labeled_string
for things like https://phabricator.services.mozilla.com/D213115 as advised on #glean
(Note for others, labeled_counter would have to be carefully set lifetime: application
and tie to a once-in-a-run event - since counter can only add, not set, and we need to make sure to do it only once.)
Perhaps one other class that could use some more eyes is how I use event
- there are a couple of these, like https://phabricator.services.mozilla.com/D213123 (the probe itself is not ideal and should be reworked in another bug)
Assignee | ||
Comment 28•5 months ago
|
||
Comment 29•5 months ago
|
||
Both of them look just fine to me, with some small things to watch out for. Where this will become interesting is analysis: will you be able to answer the questions you have with data in these shapes.
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Assignee | ||
Comment 30•4 months ago
|
||
One thing that came to mind is that using a "tb." prefix probably isn't the best idea now, since there can't be (future) metrics files for other folders - say for calendar/ - using the same prefix. I guess we should use "mail." for the ones in the mail/ folder
Assignee | ||
Updated•4 months ago
|
Comment 31•4 months ago
|
||
Comment 32•4 months ago
|
||
(In reply to Magnus Melin [:mkmelin] from comment #30)
One thing that came to mind is that using a "tb." prefix probably isn't the best idea now, since there can't be (future) metrics files for other folders - say for calendar/ - using the same prefix. I guess we should use "mail." for the ones in the mail/ folder
Oh yes, that's an excellent point. Especially since all datasets will be namespaced to the application id (which I assume will be thunderbird
) so including tb.
could be redundant. Sorry, I should've caught that naming smell when you asked for review.
Comment 33•4 months ago
|
||
Oh, though I should mention, you can use the same category in multiple files. There's no restriction there. Though the pipeline will complain if you have a fully-duplicated metric name.
Comment 34•4 months ago
|
||
What are the next steps here?
Should we request 128 uplift?
Do you want to remove the tb.
prefix?
Assignee | ||
Comment 35•4 months ago
|
||
I'll change/remove the prefix.
We should uplift to 128, but I'd wait until legal is finished so we can properly check data is getting sent correctly first.
:chutten, IIRC you mentioned earlier the Thunderbird app id also needs to be added to an allow list (in the data pipeline somewhere) so tb data wouldn't get discarded. Do you recall what that was, and how should that be handled?
Comment 36•4 months ago
|
||
More than recalling it, we've documented it! https://mozilla.github.io/glean/book/user/adding-glean-to-your-project/index.html
I think the specific step you're after is 4, but the whole thing's a decent checklist to doublecheck.
Assignee | ||
Comment 37•4 months ago
|
||
Stop using the tb. prefix, and put the probes in component relative metrics.yaml files
Updated•4 months ago
|
Assignee | ||
Updated•4 months ago
|
Comment 38•4 months ago
|
||
Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/cfb3e3498687
Distribute metrics.yaml files to where they belong. r=aleca
Comment 39•3 months ago
|
||
Candidate then for 128.1.0? Or do you have more coming?
Comment 40•3 months ago
|
||
We've been receiving telemetry for this in the data pipeline for a few weeks now but it's been coming with the firefox-desktop
app namespace so it's all landing in bigquery right now (but not in the correct columns because the metrics weren't added to probe-scraper). I want to check if this is intended or possibly side effect of reusing firefox code. Reading the conversation above, it sounds like this isn't intended.
Comment 41•3 months ago
|
||
Thanks for the report.
This definitely wasn't the intended outcome.
Alessio, can you advice on the steps to take to fix this? Is following the steps to add the probe-scraper all we need?
Comment 42•3 months ago
|
||
(In reply to Ben Wu [:benwu] from comment #40)
We've been receiving telemetry for this in the data pipeline for a few weeks now but it's been coming with the
firefox-desktop
app namespace
Hey Chris, aren't we changing the app id somewhere for this?
Comment 43•3 months ago
|
||
(In reply to Alessandro Castellani [:aleca] from comment #41)
Is following the steps to add the probe-scraper all we need?
No, we need legal clearance for that step
This is a different problem I believe: thunderbird should be using a different app id
Comment 44•3 months ago
|
||
The only place where that app id is set is in BrowserGlue
which I was under the understanding that Thunderbird didn't actually run. If Thunderbird does run those idle tasks, then we're going to need an if (<is thunderbird>) { return; }
somewhere around here. (( Actually, looks like those tasks have condition
support, so maybe we should prefer condition: <isn't thunderbird>
))
Comment 45•3 months ago
|
||
We seem to call that from our own glue: https://searchfox.org/comm-central/rev/d9f4b21312781d3abb9c88cade1d077b9e1622f4/mail/components/MailGlue.sys.mjs#837
So I assume we'd have to pass in an app ID override there (based on https://searchfox.org/mozilla-central/rev/e637cd67f98ed4272d13a96db9a7674689122dcb/toolkit/components/glean/xpcom/nsIFOG.idl#23)?
Comment 46•3 months ago
|
||
That's what's waiting on Legal before we do it. For now, if there's something e.g. in AppConstants
we could check as a task condition
, that could be ideal
Comment 47•3 months ago
|
||
(In reply to Chris H-C :chutten from comment #46)
That's what's waiting on Legal before we do it. For now, if there's something e.g. in
AppConstants
we could check as a taskcondition
, that could be ideal
Adding a different app id, without enabling it into the pipeline, it's fine too I believe
Assignee | ||
Comment 48•3 months ago
|
||
Still waiting on legal and such, so we can properly verify stuff, so no uplifts yet.
Comment 49•3 months ago
|
||
(In reply to Magnus Melin [:mkmelin] from comment #48)
Still waiting on legal and such, so we can properly verify stuff, so no uplifts yet.
We got the go-ahead from legal - regardless, we still need to uplift, as this is currently reporting using the wrong app id.
Comment 50•3 months ago
|
||
I mean we need to uplift bug 1910837
Assignee | ||
Comment 51•3 months ago
|
||
Thanks, I've requested beta uplift for that one.
(Will get to this one later, but no time right now.)
Comment 52•3 months ago
|
||
(In reply to Magnus Melin [:mkmelin] from comment #51)
Thanks, I've requested beta uplift for that one.
(Will get to this one later, but no time right now.)
Thank you! Yes, that's fine, the important one was the other one :-)
Description
•