2
edits
Changes
no edit summary
==Data Format==
===Overview===
Data will be collected as a stream of events, with the exception of a user profile that is collected once every browser session. We will define several event types that will have predefined schemas. Having these schemas will allow us to leave out the label for each piece of data in the event, compacting the amount of data that we send to the server. We will be able to throttle data collection based on the event type, so that verbose events can be turned on and off when we want. The tentative event types and associated schemas are listed below. (Note: the list is still very much in flux and will likely change.)
===Profile===
The profile will be collected every browser session, to pick up changes periodically. The data included in the profile is as follows:
* Memory
* OS
* Firefox version
* Talkback user ID
* extensions (maybe only those from addons.mozilla.org)
* plugins
* screen resolution
* default browser
* install date
* default search engine
===Load Event===
* type = [back, typed, bookmark, script...]
* target = [current, new window, new tab...]
* load time
* cache size before/after load
* content viewer size estimate
* cache hit
* session history index
* last visit date
* tagged/bookmarked
===UI Event===
* action = [click, key, drag, drop...]
* target = [some kind of ID, possibly XUL name]
===Garbage Collection===
* number/size of objects reachable
* time spent doing garbage collection
===Startup/Shutdown===
* time taken
===Places UI Event===
We'll have to be sure not to duplicate data here between the UI Event and the Places UI Event. This could potentially be an extension of the regular UI Event.
* node types expanded/clicked
* periods of time searched
===Autocomplete===
We may try to fit this into the schema of another event type.
* how far down the list?
* match but typed anyway?
===Open Issues===
* We may want to consolidate some of these events into summary statistics, to compact the amount of data we are collecting. However, this may not be necessary since we will be able to throttle the data collection on a per event type.
* To allow extensions to collect data via this system, we will need to define a generic event type or a way to extend the list of predefined events. This is TBD.
* The event types listed above are still in flux and may be combined or removed.
===Overview===
Data will be collected as a stream of events, with the exception of a user profile that is collected once every browser session. We will define several event types that will have predefined schemas. Having these schemas will allow us to leave out the label for each piece of data in the event, compacting the amount of data that we send to the server. We will be able to throttle data collection based on the event type, so that verbose events can be turned on and off when we want. The tentative event types and associated schemas are listed below. (Note: the list is still very much in flux and will likely change.)
===Profile===
The profile will be collected every browser session, to pick up changes periodically. The data included in the profile is as follows:
* Memory
* OS
* Firefox version
* Talkback user ID
* extensions (maybe only those from addons.mozilla.org)
* plugins
* screen resolution
* default browser
* install date
* default search engine
===Load Event===
* type = [back, typed, bookmark, script...]
* target = [current, new window, new tab...]
* load time
* cache size before/after load
* content viewer size estimate
* cache hit
* session history index
* last visit date
* tagged/bookmarked
===UI Event===
* action = [click, key, drag, drop...]
* target = [some kind of ID, possibly XUL name]
===Garbage Collection===
* number/size of objects reachable
* time spent doing garbage collection
===Startup/Shutdown===
* time taken
===Places UI Event===
We'll have to be sure not to duplicate data here between the UI Event and the Places UI Event. This could potentially be an extension of the regular UI Event.
* node types expanded/clicked
* periods of time searched
===Autocomplete===
We may try to fit this into the schema of another event type.
* how far down the list?
* match but typed anyway?
===Open Issues===
* We may want to consolidate some of these events into summary statistics, to compact the amount of data we are collecting. However, this may not be necessary since we will be able to throttle the data collection on a per event type.
* To allow extensions to collect data via this system, we will need to define a generic event type or a way to extend the list of predefined events. This is TBD.
* The event types listed above are still in flux and may be combined or removed.
