Closed
Bug 942279
(mobile-ui-telemetry)
Opened 11 years ago
Closed 4 years ago
[meta] Add probes for Mobile UI Telemetry
Categories
(Firefox for Android Graveyard :: General, task)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: liuche, Unassigned)
References
()
Details
(Keywords: meta)
Attachments
(1 file, 1 obsolete file)
(deleted),
patch
|
Details | Diff | Splinter Review |
No description provided.
Reporter | ||
Comment 1•11 years ago
|
||
This adds probes for BrowserApp being in the foreground, and events when the default search engine is changed.
Additional probes of interest as suggested in bug 932092:
* Opening URLbar
* Tapping a thumbnail in topsites
* Adding a session that starts in onCreate and ends when we get a Gecko:Ready message
* Adding a session that starts when AboutHome is shown and ends when it hides
Updated•11 years ago
|
Hardware: ARM → All
Reporter | ||
Comment 2•11 years ago
|
||
Unbitrotting from the renaming of Ui=>UI in bug 932092.
Attachment #8337005 -
Attachment is obsolete: true
Reporter | ||
Comment 3•11 years ago
|
||
Morphing this into a meta bug, to keep track of our UI telemetry probes.
Updated•11 years ago
|
Reporter | ||
Comment 4•11 years ago
|
||
Overview and guidelines on writing probes: https://wiki.mozilla.org/Mobile/Fennec/Android/UITelemetry
UI Telemetry probe asks: https://etherpad.mozilla.org/FxATelemetry
Ian, what are the most important features that we'd want telemetry for? Do you think you could file bugs for the ones that you'd like us to get done in the next week?
Flags: needinfo?(ibarlow)
Reporter | ||
Updated•11 years ago
|
Flags: needinfo?(ibarlow)
Reporter | ||
Comment 5•10 years ago
|
||
Flaviu, you asked about doing QA for this. The best way to do this at the moment is to watch for Android adb logcat [1] statements, and make sure the logging is happening when expected. However, this only works for Java probes (e.g., not bug 1007095, bug 1006670, or most of bug 986095, where the probes are added in JS).
Each of the bugs should describe under what conditions the probes should be firing (event, starting/stopping a UI session).
For example, a log statement for an event will have a logtag of "Telemetry" and be of the form of "SendUIEvent: action = <action> method = <method> timestamp = <timestamp> extras = <extras>"
Or see:
http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/Telemetry.java#127
Let me know if you have any other questions or want clarification - if they're specific to a particular probe, feel free to post them in the dependent bugs.
[1] https://wiki.mozilla.org/Mobile/Fennec/Android#Using_logcat
I tend to use Eclipse because it's really easy to filter output, but you can also set commandline adb logcat to filter on different logtags, I think.
Flags: needinfo?(flaviu.cos)
Comment 6•10 years ago
|
||
Thanks for the info. I managed to verify some of the depending bugs.
I will continue to verify only the probes implemented in java since I can not verify the ones implemented in javascript.
Flags: needinfo?(flaviu.cos)
Updated•10 years ago
|
QA Contact: flaviu.cos
Updated•10 years ago
|
Updated•6 years ago
|
Type: defect → task
Comment 8•4 years ago
|
||
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•