334
edits
No edit summary |
No edit summary |
||
(4 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
The client config is provided by the server. An opportunity to reconfigure the client happens every time the extension uploads data. This gives us the opportunity to scale up or down (or turn off completely) any data sent to us by reconfiguring the extension on the fly. | The client config is provided by the server. An opportunity to reconfigure the client happens every time the extension uploads data. This gives us the opportunity to scale up or down (or turn off completely) any data sent to us by reconfiguring the extension on the fly. | ||
* | * CONF-01 - respond with a config upon upload conforming to [http://mxr.mozilla.org/seamonkey/source/extensions/metrics/src/nsMetricsService.cpp#667 how the extension handles responses] | ||
* allow different configs for various samples of uploading clients | * CONF-02 - allow different configs for various samples of uploading clients | ||
= Backend = | = Backend = | ||
Take uicommand event stream and put it in to an aggregate database, query-able over date ranges. | |||
* | * BACK-01 Store uicommand XML stream into aggregate query-able database. ([https://bugzilla.mozilla.org/show_bug.cgi?id=399869#c3 example data]) | ||
= Frontend = | = Frontend = | ||
* | * FRONT-01 - Show aggregate [[Browser_Metrics:Data_Collectors#UI_Event|uicommands]] over a daterange (ex: sorted list of uicommands by X users on October 17th, 2007) | ||
= API = | = API = | ||
* | * No api requirements for V01 |
edits