Hi everyone,
I'm currently looking at FxA user metrics this quarter and have a few
thoughts around some ideas. Let me kick off by just having a brief outline
so you get an idea of what's needed.
"All services attached to FxA should report metrics on user activity
in a consistent, privacy-respecting manner. We should have dashboards that
allow us to measure success and monitor for problems."
This may or may not be the exact goal we're reaching for, but it's
currently a good statement to aim for. Other questions we might like to ask
and answer in the future are:
* how many users signed up this month?
* how many users used a particular service (e.g. Hello, Sync)?
* how many users logged in with a mobile device?
* (perhaps other questions we don't yet know about)
To do this we need to figure out how to make this happen. By logging 'user
events' we should be able to take advantage of the regular data pipeline
running through Heka/ElasticSearch/Kibana and/or any other
Reporting/MapReduce plus custom dashoards as aimed for by the Data Pipeline
v2 [1]. Therefore this email is mainly concentrating on what we do at the
edges, i.e. our application servers.
We would love to correlate users across services so we need something which
allows us to do this. Of course the uid of a user is the obvious answer but
one that would raise some privacy questions. Perhaps we could post-process
these in the data pipeline into something else, or we can log something
locally which we could use to correlate that same user to another service
(but not back to the user him/herself). The idea of a Metrics ID has been
raised which is a one-way mapping from uid to Metrics ID (am leaving out
any implementation details for now). Of course, all services would need to
know how to make that MetricsID if it was logged at the edge, but if the
uid was post-processed in the data pipeline this could be done centrally.
I'm sure there are other solutions too ... ideas welcome!
Does this sound like it could work (both technically but keeping an eye on
what we against each metrics ID)? I am deliberately leaving off any details
of how this could work since I'm currently more interested in what you all
think of this idea. What are the gotchyers? Can anyone see problems we'll
hit? Does this all sound reasonable?
Cheers,
Andy
[1] https://wiki.mozilla.org/CloudServices/DataPipeline#V2_Pipeline
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct
