User:Polvi/InstrumentationServer:RequirementsV01: Difference between revisions
Jump to navigation
Jump to search
(→Config) |
|||
| Line 10: | Line 10: | ||
= Backend = | = Backend = | ||
Take uicommand event stream and put it in to an aggregate database, query-able over date ranges. | |||
* Serialize XML into a | * Serialize XML into a aggregate database ([https://bugzilla.mozilla.org/show_bug.cgi?id=399869#c3 example data]) | ||
= Frontend = | = Frontend = | ||
Revision as of 04:01, 31 October 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.
- Serialize XML into a aggregate database (example data)
Frontend
- Show cronological event stream based on guid (ex: guid XYZ clicked the back button, then opened a new tab, then bookmarked)
- Show aggregate uicommands over a specific time (ex: 3000 back button clicks for 100 users on October 17th, 2007)
API
- Query frontend information via API and have results represented in XML