User:Polvi/InstrumentationServer:RequirementsV01: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 12: | Line 12: | ||
Take uicommand event stream and put it in to an aggregate database, query-able over date ranges. | Take uicommand event stream and put it in to an aggregate database, query-able over date ranges. | ||
* | * Store uicommand XML stream into aggregate query-able database. ([https://bugzilla.mozilla.org/show_bug.cgi?id=399869#c3 example data]) | ||
= Frontend = | = Frontend = | ||
* Show aggregate [[Browser_Metrics:Data_Collectors#UI_Event|uicommands]] over a | * 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 | ||
Revision as of 17:22, 1 November 2007
Config
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.
- prepare a config upon upload conforming to how the extension handles responses
- allow different configs for various samples of uploading clients
GUID
The metrics extension sends a header with a client ID specifying a unique extension install.
- Correlate unique extension installs to data using the Client ID
Backend
Take uicommand event stream and put it in to an aggregate database, query-able over date ranges.
- Store uicommand XML stream into aggregate query-able database. (example data)
Frontend
- Show aggregate uicommands over a daterange (ex: sorted list of uicommands by X users on October 17th, 2007)
API
- No api requirements for V01