Collecting specific information for the metlog team

[Victor Ng]

Hi everyone,

I'd like to gather some specific requirements for the kinds of
information you'd like applications to collect, but for whatever reason
- we currently don't.

An example of this is: "We'd like to see the breakdown of Sync users
over time, broken down by version ffx version and sync client version."

I have some notes for JPake and for Sync - but please send any
requirements our way. If you can think of something you want measured,
but don't have a way of doing it - or if you want better ways of
capturing that data let me know!

Thanks!
vic
_______________________________________________
Services-dev mailing list
Servic...@mozilla.org
https://mail.mozilla.org/listinfo/services-dev

[Richard Newman]

See previous threads for context:

http://groups.google.com/group/mozilla-services-dev/browse_thread/thread/fe3158fcc4ed298b/

http://groups.google.com/group/mozilla-services-dev/browse_thread/thread/391ad8ba52f424a/

From the perspective of debugging Sync, I'm interested in:

* Completion rates per stage of setup, broken down by client type and version. (Firefox version and Sync version are interchangeable right now.)
* Sync frequencies and payload sizes per collection, similarly. ("Firefox 13 is hitting meta/global every 5 minutes…")
* Number of requests per sync, similarly.
* Frequency of client sync collisions: that is, how often do users have a second sync begin before a first sync on another device has finished?
* Frequency of no-op syncs: requests to info/collections that aren't immediately followed by any other requests.

Note that most of these are time-based analysis. In all cases we are interested in trends as versions change.

Thanks for askin'!

[Toby Elliott]

On Mar 9, 2012, at 4:03 PM, Richard Newman wrote:

> From the perspective of debugging Sync, I'm interested in:
>
> * Completion rates per stage of setup, broken down by client type and version. (Firefox version and Sync version are interchangeable right now.)

This one probably won't happen, due to the radical revamp of setup coming up.

> * Sync frequencies and payload sizes per collection, similarly. ("Firefox 13 is hitting meta/global every 5 minutes…")

Huge +1 for this one.

I'd also like a histogram of sync frequency (number of initiated syncs in a 24-hour period per-user-per-client)

Toby

[Ryan Kelly]

On 09/03/12 15:44, Victor Ng wrote:
> Hi everyone,
>
> I'd like to gather some specific requirements for the kinds of
> information you'd like applications to collect, but for whatever reason
> - we currently don't.
>
> An example of this is: "We'd like to see the breakdown of Sync users
> over time, broken down by version ffx version and sync client version."
>
> I have some notes for JPake and for Sync - but please send any
> requirements our way. If you can think of something you want measured,
> but don't have a way of doing it - or if you want better ways of
> capturing that data let me know!

Some useful metrics discussed with Toby yesterday for sync:

* What percentage of requests fail authentication due to an
expired token?

* What percentage of requests to /info/collections return
a 304 response vs a 200 response.

Cheers,

Ryan