Difference between revisions of "Platform Team/Usage Statistics"

From Sugar Labs
Jump to navigation Jump to search
Line 1: Line 1:
 
== Summary ==
 
== 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).
+
Sugar usage statistics might be very useful from, e.g., an educational or research point of view. Statistics might be anonymous or personalized (by taking special efforts to keep information secure and local only for a particular deployment).
  
 
== Statistics ==
 
== Statistics ==
  
All types of statistics are identified by IDs in dot separated hierarchy to make it possible to refer to the particular type or types level.
+
All types of statistics are identified by IDs in a dot separated hierarchy. This makes it possible to refer to the particular type or level of data.
  
 
* {{Code|shell}}<br>Shell related stats.
 
* {{Code|shell}}<br>Shell related stats.
Line 12: Line 12:
 
** {{Code|shell.collab}}<br>Collaboration related stats in Shell.
 
** {{Code|shell.collab}}<br>Collaboration related stats in Shell.
 
*** {{Code|shell.collab.buddies}}<br>Number of buddies in the Neighborhood view.
 
*** {{Code|shell.collab.buddies}}<br>Number of buddies in the Neighborhood view.
* {{Code|activity}}<br>Activities related stats; specified only for particular activity.
+
* {{Code|activity}}<br>Activities related stats; specified only for the particular activity.
 
** {{Code|activity.run}}<br>Activity is run.
 
** {{Code|activity.run}}<br>Activity is run.
 
** {{Code|activity.active}}<br>Activity window is active.
 
** {{Code|activity.active}}<br>Activity window is active.
Line 24: Line 24:
 
=== Monitor ===
 
=== 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]].
+
The usage statistics will be gathered by sniffing DBus messages in the [[Sugar_Server_Kit/sugar-client|sugar-client]] program launched with the {{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 ===
 
=== Collector ===
  
 
=== Analyzer ===
 
=== Analyzer ===

Revision as of 11:30, 24 November 2011

Summary

Sugar usage statistics might be very useful from, e.g., an educational or research point of view. Statistics might be anonymous or personalized (by taking special efforts to keep information secure and local only for a particular deployment).

Statistics

All types of statistics are identified by IDs in a dot separated hierarchy. This makes it possible to refer to the particular type or level of data.

  • shell
    Shell related stats.
    • shell.run
      Shell process is run.
    • shell.active
      Shell or activity window is active.
    • shell.collab
      Collaboration related stats in Shell.
      • shell.collab.buddies
        Number of buddies in the Neighborhood view.
  • activity
    Activities related stats; specified only for the particular activity.
    • activity.run
      Activity is run.
    • activity.active
      Activity window is active.
    • activity.collab
      Collaboration related stats for activities.
      • activity.collab.buddies
        Number of buddies activity is interacting with.
  • system
    System related stats.
    • system.uptime
      System uptime value.

Implementation

Monitor

The usage statistics will be gathered by sniffing DBus messages in the sugar-client program launched with the monitor command. The sugar-client will stay in daemon mode, and send collected and filtered data to the sugar-server.

Collector

Analyzer