Missing partner code in metrics.search_count metric
Categories
(Firefox for Android :: Search, defect)
Tracking
()
People
(Reporter: dpop, Assigned: RJ)
References
(Regression)
Details
(Keywords: regression)
Attachments
(3 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-release+
|
Details | Review |
Steps to reproduce
- Launch any custom debug builds hardcoded aura-001, dt-002, dt-003 distribution IDs.
- Turn off the “Use remote settings production server" option in Secret Settings.
- Restart the app.
- Set the region to US or a region outside US (e.g. FR, DE, JP) using the debug drawer.
- Perform a search using the Google search engine.
- Sent the metrics ping type using the Glean Debug Tools and check the metrics in Glean.
Expected behavior
metrics.search_count should be recorded with a key of google-b-1-ar.<source> for the US, or google-b-ar.<source> for the rest of the world:
e.g. for a region outside US:
"metrics.search_count": {
"google-b-ar.action": 1
Actual behavior
The partner code is missing.
e.g. for a region outside US:
"metrics.search_count": {
"google.action": 6
Device information
Firefox version: Custom debug builds, hardcoded aura-001, dt-002, dt-003 distribution IDs provided on slack
Android device model: Google Pixel 8 Pro (Android 15)
Additional information
Tested on multiple regions set using the Debug Drawer/devices settings and VPN.
Tested with “Use remote settings production server" option from Secret Settings enabled and disabled.
Comment 1•21 days ago
|
||
This appears to have been caused by the search consolidation work, and is reflected in the telemetry we're seeing.
The key used for telemetry in this case should be the search engine identifier plus the suffix if there is one (something equivalent to this).
Sarah, would you be able to take a look or find someone who could look please?
Assignee | ||
Comment 2•21 days ago
|
||
Assignee | ||
Updated•21 days ago
|
Comment 3•20 days ago
|
||
Set release status flags based on info from the regressing bug 1969324
Comment 6•19 days ago
|
||
The patch landed in nightly and beta is affected.
:RJ, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox142
towontfix
.
For more information, please visit BugBot documentation.
Assignee | ||
Comment 7•19 days ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D258075
Updated•19 days ago
|
Comment 8•19 days ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined: Wrong telemetry would be recorded when searching
- Code covered by automated testing: yes
- Fix verified in Nightly: no
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: Check if the correct telemetry is recorded when searching
- Risk associated with taking this patch: Very low
- Explanation of risk level: Modifies existing telemetry
- String changes made/needed: No
- Is Android affected?: no
Assignee | ||
Updated•19 days ago
|
Updated•18 days ago
|
Updated•18 days ago
|
Reporter | ||
Comment 10•17 days ago
|
||
Verified as fixed on latest Nightly 143.0a1 from 07/25 with Motorola Moto G30 (Android 12):
Nightly "metrics.search_count": {
"google-b-1-m.action": 1
},
Reporter | ||
Comment 11•14 days ago
|
||
Verified as fixed in Beta 142.0b3 with Google Pixel 8 Pro (Android 15):
Beta
"metrics.search_count": {
"google-b-1-m.action": 1
Comment 12•13 days ago
|
||
Do we need to uplift this to Release as well for 141.0.2?
Assignee | ||
Comment 13•13 days ago
•
|
||
Do we need to uplift this to Release as well for 141.0.2?
Yes
Assignee | ||
Comment 14•13 days ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D258075
Updated•13 days ago
|
Comment 15•13 days ago
|
||
firefox-release Uplift Approval Request
- User impact if declined: Wrong telemetry would be recorded when searching
- Code covered by automated testing: yes
- Fix verified in Nightly: yes
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: Check if the correct telemetry is recorded when searching
- Risk associated with taking this patch: Very low
- Explanation of risk level: Modifies existing telemetry
- String changes made/needed: No
- Is Android affected?: no
Updated•13 days ago
|
Updated•11 days ago
|
Comment 16•11 days ago
|
||
The patch failed to land on the release branch, could you rebase and update your uplift request? Thanks
Updated•10 days ago
|
Comment 18•10 days ago
|
||
uplift |
Reporter | ||
Comment 19•6 days ago
|
||
Verified as fixed in dot release 141.0.2 with Google Pixel 8 Pro (Android 15):
"metrics.search_count": {
"google-b-1-m.action": 1
Reporter | ||
Updated•6 days ago
|
Description
•