User Story: As a product manager, I want to know the number of active daily users of FxA, so that I can track the growth and health of FxA. Acceptance Criteria: 1. PMs of Sync, FxOS, Android, Marketplace, etc. have access to a dashboard showing them a measure that reasonably approximates average daily users of FxA over time. Timeframe: Required by the time FxA goes live, which will be FxA Sync on Fx29
Component: Operations: Metrics/Monitoring → Server: Firefox Accounts
Summary: [Story] FxAccounts Active Daily Users (ADU) → [Metrics Story] FxAccounts Active Daily Users (ADU)
For ADU, we can count assertions verified, bucketed by user id. (Or we could count certificates signed by the fxa-auth-server). For now, certificates expire every 24 hours. Discussed in this thread: https://mail.mozilla.org/pipermail/dev-fxacct/2014-February/000541.html
We should be able to get the data from the fxa-auth-server request summary log line: https://github.com/mozilla/fxa-auth-server/issues/541
kparlante on wiki: heka can do processing to count unique userid's/day, so that userid is not stored in elastic search trink response: 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.
As the active daily users grow this plugin will run out of memory. If we want to continue to use it we will have to switch it to an estimate (like we do with the frequent items counter) This version only displays "All" but it sounds like you would like it broken out by service too. https://heka.fxa.us-west-2.dev.mozaws.net/#sandboxes/FxaSandboxManager-FxaActive/outputs/FxaSandboxManager-FxaActive.ActiveDailyUsers.cbuf
Good enough for go live (accessible from statusboard), but not fully automated so not done.
Depends on: 1001014
Story accomplished: https://metrics.fxa.us-west-2.prod.mozaws.net/accounts-dashboard/ Git repo: https://github.com/mozilla/accounts-dashboard
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.