UI Telemetry is event data and one of the questions asked of event data is what constitutes a "session". This is not the UI Telemetry "session", which is used to scope events. We could use probes for application-level foreground and background as a way to help define sessions.
Created attachment 8720844 [details] [diff] [review] track-application-sessions v0.1 Simple patch to add application foreground/background into the event data flow
Assignee: nobody → mark.finkle
Attachment #8720844 - Flags: review?(margaret.leibovic)
Attachment #8720844 - Flags: review?(margaret.leibovic) → review+
Comment on attachment 8720844 [details] [diff] [review] track-application-sessions v0.1 Approval Request Comment [Feature/regressing bug #]: [User impact if declined]: Gives us better session scoping in our event analysis [Describe test coverage new/current, TreeHerder]: [Risks and why]: Low risk patch only adds probes. [String/UUID change made/needed]: None
Status: NEW → RESOLVED
Last Resolved: 2 years ago
status-firefox47: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 47
status-firefox45: --- → affected
status-firefox46: --- → affected
Comment on attachment 8720844 [details] [diff] [review] track-application-sessions v0.1 I would prefer to see that riding the train from 46 as we are late in the cycle (only taking important fixes).
has problems uplifting to aurora: warning: conflicts while merging mobile/android/base/java/org/mozilla/gecko/TelemetryContract.java! (edit, then use 'hg resolve --mark') can you take a look, thanks!
status-firefox45: affected → wontfix
status-firefox46: affected → fixed
You need to log in before you can comment on or make changes to this bug.