User:Polvi/InstrumentationServer:RequirementsV01: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
= GUID =
= Config =
The metrics extension sends a header with a client ID specifying a unique extension install.
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.  
* Correlate unique extension installs to data using the  [[Browser_Metrics:Data_Collection_Service#Client_ID|Client ID]]
 
* 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]
* CONF-02 - allow different configs for various samples of uploading clients


= Backend =
= Backend =
* Serialize XML into a database
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 =
* Show cronological event stream based on guid (ex: guid XYZ clicked the back button, then opened a new tab, then bookmarked)
* 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)
* Show aggregate [[Browser_Metrics:Data_Collectors#UI_Event|uicommands]] over a specific time (ex: 3000 back button clicks for 100 users on October 17th, 2007)


= API =
= API =
* Query frontend information via API and have results represented in XML
* No api requirements for V01

Latest revision as of 21:37, 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.

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. (example data)

Frontend

  • FRONT-01 - Show aggregate uicommands over a daterange (ex: sorted list of uicommands by X users on October 17th, 2007)

API

  • No api requirements for V01
Retrieved from "https://wiki.allizom.org/index.php?title=User:Polvi/InstrumentationServer:RequirementsV01&oldid=72832"