Closed Bug 1978320 Opened 21 days ago Closed 19 days ago

Missing partner code in metrics.search_count metric

Categories

(Firefox for Android :: Search, defect)

Firefox 140
All
Android
defect

Tracking

()

VERIFIED FIXED
143 Branch
Tracking Status
firefox141 --- verified
firefox142 --- verified
firefox143 --- verified

People

(Reporter: dpop, Assigned: RJ)

References

(Regression)

Details

(Keywords: regression)

Attachments

(3 files)

Steps to reproduce

  1. Launch any custom debug builds hardcoded aura-001, dt-002, dt-003 distribution IDs.
  2. Turn off the “Use remote settings production server" option in Secret Settings.
  3. Restart the app.
  4. Set the region to US or a region outside US (e.g. FR, DE, JP) using the debug drawer.
  5. Perform a search using the Google search engine.
  6. 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.

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?

Flags: needinfo?(skhan)
Keywords: regression
Regressed by: 1969324
Summary: [Aura & Digital Turbine Distribution] Missing partner code in metrics.search_count metric → Missing partner code in metrics.search_count metric
Version: Firefox 142 → Firefox 140
See Also: → 1978337
Assignee: nobody → rmalicdem
Status: NEW → ASSIGNED

Set release status flags based on info from the regressing bug 1969324

Status: ASSIGNED → RESOLVED
Closed: 19 days ago
Resolution: --- → FIXED
Target Milestone: --- → 143 Branch

The patch landed in nightly and beta is affected.
:RJ, is this bug important enough to require an uplift?

For more information, please visit BugBot documentation.

Flags: needinfo?(rmalicdem)
Attachment #9502436 - Flags: approval-mozilla-beta?

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
Flags: qe-verify+
See Also: → 1978845
Flags: needinfo?(rmalicdem)
Attachment #9502436 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

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
},

Flags: needinfo?(skhan)

Verified as fixed in Beta 142.0b3 with Google Pixel 8 Pro (Android 15):

Beta
"metrics.search_count": {
"google-b-1-m.action": 1

Status: RESOLVED → VERIFIED
Flags: qe-verify+

Do we need to uplift this to Release as well for 141.0.2?

Flags: needinfo?(rmalicdem)

Do we need to uplift this to Release as well for 141.0.2?

Yes

Flags: needinfo?(rmalicdem)
Attachment #9503852 - Flags: approval-mozilla-release?

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
Flags: qe-verify+
Blocks: 1978337
See Also: 1978337
Attachment #9503852 - Flags: approval-mozilla-release? → approval-mozilla-release+

The patch failed to land on the release branch, could you rebase and update your uplift request? Thanks

Flags: needinfo?(rmalicdem)

Uplift request rebased!

Flags: needinfo?(rmalicdem)

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

Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: