Closed
Bug 1898552
Opened 6 months ago
Closed 5 months ago
Add support for Nimbus' recorded targeting context
Categories
(Fenix :: Experimentation and Telemetry, enhancement)
Tracking
(firefox129 fixed)
RESOLVED
FIXED
129 Branch
Tracking | Status | |
---|---|---|
firefox129 | --- | fixed |
People
(Reporter: charlie, Assigned: charlie)
References
Details
Attachments
(2 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
2.37 KB,
text/plain
|
travis_
:
data-review+
|
Details |
- Define
recorded_nimbus_context
object metric - Define and use
RecordedNimbusContext
Kotlin object and pass it through to Nimbus
See EXP-4446 for more details.
Assignee | ||
Comment 1•6 months ago
|
||
Updated•5 months ago
|
Attachment #9403560 -
Attachment description: WIP: Bug 1898552: Define and use Nimbus RecordedContext object → Bug 1898552: Define and use Nimbus RecordedContext object r?lina,barret,janerik
Assignee | ||
Comment 2•5 months ago
|
||
Attachment #9406713 -
Flags: data-review?(tlong)
Comment 3•5 months ago
|
||
Comment on attachment 9406713 [details]
data review request
Data Review
- Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?
Yes, through the metrics.yaml file and the Glean Dictionary.
- Is there a control mechanism that allows the user to turn the data collection on and off?
Yes, through the data preferences in the application settings.
- If the request is for permanent data collection, is there someone who will monitor the data over time?
Permanent collection to be monitored by chumphreys@mozilla.com & project-nimbus@mozilla.com
- Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?
Category 2
- Is the data collection request for default-on or default-off?
Default-on
- Does the instrumentation include the addition of any new identifiers (whether anonymous or otherwise; e.g., username, random IDs, etc. See the appendix for more details)?
No
- Is the data collection covered by the existing Firefox privacy notice?
Yes
- Does the data collection use a third-party collection tool?
No
Result
data-review+
Attachment #9406713 -
Flags: data-review?(tlong) → data-review+
Pushed by chumphreys@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/fbc9786ba381
Define and use Nimbus RecordedContext object r=lina,android-reviewers,barret,Roger
Comment 5•5 months ago
|
||
Backed out for causing toolchain failures in BrowserFragment.kt.
- Backout link
- Push with failures
- Failure Log
- Failure line: file:///builds/worker/workspace/build/src/mobile/android/fenix/app/src/main/java/org/mozilla/fenix/browser/BrowserFragment.kt:344:40: error: Unresolved reference: cancelTapped
Flags: needinfo?(chumphreys)
Comment 6•5 months ago
•
|
||
I think I know what happened here to cause this to be backed out: you inserted your event in the metrics.yaml in a place that caused cancel_tapped
to change its metric category, and thus its generated metric name. This lead to the cancelTapped
object not being found in the calling code.
Pushed by chumphreys@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/757bbd386da2
Define and use Nimbus RecordedContext object r=lina,android-reviewers,barret,Roger,TravisLong
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
status-firefox129:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 129 Branch
Assignee | ||
Updated•4 months ago
|
Flags: needinfo?(chumphreys)
You need to log in
before you can comment on or make changes to this bug.
Description
•