Closed Bug 1036551 Opened 11 years ago Closed 9 years ago

Loop total users (cumulative): json output

Categories

(Cloud Services :: Operations: Metrics/Monitoring, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kparlante, Assigned: whd)

References

Details

(Whiteboard: [qa-])

We need to track total cumulative users for the loop dashboard.
Tarek, does loop have a database of unique users that we could use for the canonical number, or should we be calculating this based on the logs?
Flags: needinfo?(tarek)
We only store the call urls and hawk info associated to a given usermac, but we don't have a list of users per se (key/value store). If that can be calculated based on the logs it would be better
Flags: needinfo?(tarek)
The current plan is to track total unique uid's that are involved in successful calls, as will be logged here: https://bugzilla.mozilla.org/show_bug.cgi?id=1046236. In the meantime, we can count unique uids on all endpoints, as we are doing with daily active users. Timeframe: My understanding is that Loop is planned for FF33, which goes to Beta on 2014-09-02 and release on 2014-10-14. It would be great to have this up and running for Beta.
Assignee: nobody → mtrinkala
Summary: Loop total users (cumulative): heka filter → Loop total users (cumulative): json output
Blocks: 1052152
Whiteboard: [qa-]
(In reply to Wesley Dawson [:whd] from comment #4) > Working on this in > https://github.com/mozilla-services/puppet-config/pull/777. I'm assuming > we'll want the output format to be similar to > https://github.com/mozilla-services/puppet-config/blob/master/shared/modules/ > fxa/files/hekad/lua_filters/fxa_basic_metrics.lua. Yes, here's the proposal for the output: https://bugzilla.mozilla.org/show_bug.cgi?id=1052152 Same as basic metrics, but adding in FxOS segmentation.
Depends on: 1074468
Closing since this was delivered on the Hello dashboard - https://metrics.services.mozilla.com/loop-server-dashboard/
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.