Identity/Metrics: Difference between revisions
< Identity
Jump to navigation
Jump to search
| Line 43: | Line 43: | ||
* FHR work happening separately (Desktop: https://bugzilla.mozilla.org/show_bug.cgi?id=958561, Android: https://bugzilla.mozilla.org/show_bug.cgi?id=891600) | * FHR work happening separately (Desktop: https://bugzilla.mozilla.org/show_bug.cgi?id=958561, Android: https://bugzilla.mozilla.org/show_bug.cgi?id=891600) | ||
* PM/UX related user stories: https://id.etherpad.mozilla.org/fxacct-metrics-user-stories | * PM/UX related user stories: https://id.etherpad.mozilla.org/fxacct-metrics-user-stories | ||
*[https://bugzilla.mozilla.org/buglist.cgi?list_id=9407994&short_desc=Metrics%20Story&resolution=---&resolution=DUPLICATE&classification=Client%20Software&query_format=advanced&short_desc_type=allwordssubstr&component=Server%3A%20Firefox%20Accounts&product=Mozilla%20Services All Bugs]) | |||
== Dependencies == | == Dependencies == | ||
Revision as of 21:49, 21 February 2014
Last updated: 2014/02/21
Firefox Accounts
Stakeholders
- Product Managers, including PMs for services that rely on FxA: what does FxA adoption look like?
- UX: are users successful, where do they get stuck?
Nutshell Summary
User Stories
Priorities & open issues at a glance.
Infrastructure
- Blocking on development environment: logging stack with production data (heka, elasticsearch, kibana)
0. One Metric That Matters: Total number of Firefox Accounts
1. Accounts created per day
- https://bugzilla.mozilla.org/show_bug.cgi?id=968973
- Higher Priority Segmentations: https://bugzilla.mozilla.org/show_bug.cgi?id=968990
- Lower Priority Segmentatons: https://bugzilla.mozilla.org/show_bug.cgi?id=969003
- How is device name derived? What devices do we explicitly want to track/monitor? -trink
- "agent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.107 Safari/537.36"
- "agent":"Mozilla/5.0 (Windows NT 6.3; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0"
- "agent":"curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0 OpenSSL/0.9.8x zlib/1.2.5"
- What locales do we explicitly want to track/monitor? -trink
- Is there a fixed list of services? Again, if not which ones do we explicitly want to track/monitor -trink
- Above q's answered in above bugs -kparlante
2. Active daily users
- https://bugzilla.mozilla.org/show_bug.cgi?id=968983
- heka can do processing to count unique userid's/day, so that userid is not stored in elastic search
- note: The sandbox is intentionally resource constrained, it is highly unlikely it will have enough memory to track every active user in a day as usage increases. -trink.
UX flow analysis
Sync specific metrics
- FHR work happening separately (Desktop: https://bugzilla.mozilla.org/show_bug.cgi?id=958561, Android: https://bugzilla.mozilla.org/show_bug.cgi?id=891600)
- PM/UX related user stories: https://id.etherpad.mozilla.org/fxacct-metrics-user-stories
- All Bugs)
Dependencies
- First pass PM/UX metrics logged: https://github.com/mozilla/fxa-auth-server/issues/372
- All FxA prod data in Heka/ES/somewhere kparlante and trink can access
- fxa-auth-server API changes to collect pass through information: https://github.com/mozilla/fxa-auth-server/issues/351
Timeline
Resources
- Notes from meetings with svcops: https://id.etherpad.mozilla.org/fxa-metrics-monitoring
- QA/SE Monitoring user stories: https://id.etherpad.mozilla.org/fxa-monitoring-user-stories
- Shared Services : Describes shared services for heka/elasticsearch/kibana deployments. FxA will likely use its own deployment, based on this one.
- https://wiki.mozilla.org/ADI
- Minimum Viable Metrics : The original design for minimum set of metrics required before going live with real accounts. Original plan was WMF & Marketplace on FxOs, Sync actually went first (Desktop & Android).
Older Notes
- https://id.etherpad.mozilla.org/fxacct-metrics
- https://id.etherpad.mozilla.org/fxacct-mvm
- https://id.etherpad.mozilla.org/fxacct-mvm-details
- https://id.etherpad.mozilla.org/fxacct-metrics-fraud-detection