Closed Bug 1862927 Opened 2 years ago Closed 2 years ago

Remove duplicated metrics from service-nimbus

Categories

(Firefox for Android :: Experimentation and Telemetry, defect)

All
Android
defect

Tracking

()

RESOLVED FIXED
121 Branch
Tracking Status
firefox121 --- fixed

People

(Reporter: janerik, Assigned: jhugman)

Details

Attachments

(1 file, 1 obsolete file)

The metrics in service-nimbus (https://github.com/mozilla-mobile/firefox-android/blob/4fd5f8ff15ee73c11717ed465aa8f1519bc6df1b/android-components/components/service/nimbus/metrics.yaml) overlap with those in nimbus upstream (https://github.com/mozilla/application-services/blob/d58715194a98867372cdce8f75bd32b2e68b953b/components/nimbus/metrics.yaml)

When we recently added service-nimbus as a dependency of Android applications (https://github.com/mozilla/probe-scraper/pull/645) we run into the issue of duplicated metrics

Precisely those metrics:

  • nimbus_events.exposure
  • nimbus_events.disqualification
  • nimbus_events.enrollment
  • nimbus_events.unenrollment

We do not support the same metrics definition in different components.
Are those in service-nimbus actually recorded in that component too?
If not they can be removed and we should be able to add that to our pipeline properly.
If yes we need to come up with a plan how to handle that.

The events you mention are only relevant in the application-services component. I'll file a PR to remove them from fenix, and I'll check them in firefox-ios.

Attachment #9361866 - Attachment is obsolete: true
Status: NEW → RESOLVED
Closed: 2 years ago
Flags: qe-verify+
Resolution: --- → FIXED
Target Milestone: --- → 121 Branch
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: