Difference between revisions of "Platform Team/Usage Statistics"
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
== Implementation == | == Implementation == | ||
| − | + | === Monitor === | |
| − | + | ||
| − | + | The usage statistics will be gathered by sniffing DBus messages in [[Sugar_Server_Kit/sugar-client|sugar-client]] program launched with {{Code|monitor}} command. The {{Code|sugar-client}} will stay in daemon mode and send collected and filtered data to the [[Sugar_Server_Kit/sugar-server#collector|sugar-server]]. | |
| + | |||
| + | === Collector === | ||
| + | |||
| + | === Analyzer === | ||
Revision as of 18:59, 13 September 2011
Summary
Sugar usage statistics might be very useful from, e.g., educational point of view. Statistics might be anonymous or personalized (with taking special efforts to keep information secure and local only for particular deployment).
Statistics
- Logs if activities of sugar itself were failing.
- How long a Sugar user was on the Internet.
- How long a Sugar user was collaborating with other users:
- number of collaborators,
- durations of collaboration sessions.
- System uptime:
- total,
- time in active use (not counting time in suspend).
Implementation
Monitor
The usage statistics will be gathered by sniffing DBus messages in sugar-client program launched with monitor command. The sugar-client will stay in daemon mode and send collected and filtered data to the sugar-server.