Revision as of 23:34, 10 February 2014

Last updated: 2014/02/10

Firefox Accounts

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?
QA, Dev, Ops: Is the service responsive? Where are errors happening?
OpsSec, AppSec: Fraud detection

Unsorted
- First pass PM/UX metrics logged: https://github.com/mozilla/fxa-auth-server/issues/372
- ADU metric logged
- ADU working on dev stack
Feb 7
- All FxA prod data in Heka/ES/somewhere kparlante and trink can access
- ~~PM/UX use cases logged in bugzilla~~
- QA/SE use cases logged in bugzilla
- Roadmap/timeline documented
- ~~kparlante to document endpoints for trink, so he can configure heka for response time use cases~~
- ~~ADU metric defined~~
Feb 14
- Response time dashboard working end to end on dev stack (with production data)
Feb 21
- Accounts created/day use case working on dev stack
Feb 28

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).
Shared Services : Describes shared services for heka/elasticsearch/kibana deployments. FxA will likely use its own deployment, based on this one.
Svcops Timeline Planning
Notes from meetings with svcops: https://id.etherpad.mozilla.org/fxa-metrics-monitoring
https://wiki.mozilla.org/ADI

@@ Line 18: / Line 18: @@
 * Unsorted
 ** First pass PM/UX metrics logged: https://github.com/mozilla/fxa-auth-server/issues/372
-** ADU metric defined
 ** ADU metric logged
 ** ADU working on dev stack
@@ Line 27: / Line 26: @@
 ** Roadmap/timeline documented
 ** <strike>kparlante to document endpoints for trink, so he can configure heka for response time use cases</strike>
+** <strike>ADU metric defined</strike>
 * Feb 14
 ** Response time dashboard working end to end on dev stack (with production data)