Difference between revisions of "Sugar Network/Node Statistics"

From Sugar Labs
Jump to navigation Jump to search
Line 3: Line 3:
 
This page describes what kind of statistics [[Sugar Network]] node [[Platform_Team/Sugar_Network/Server|servers]] generate. Statistics is about the entire node server and not [[Platform_Team/Usage_Statistics|personalized]]. Besides, statistics is being targeted to edu researchers rather than service maintainers, i.e., excluding technical details that are important only for node maintaining.
 
This page describes what kind of statistics [[Sugar Network]] node [[Platform_Team/Sugar_Network/Server|servers]] generate. Statistics is about the entire node server and not [[Platform_Team/Usage_Statistics|personalized]]. Besides, statistics is being targeted to edu researchers rather than service maintainers, i.e., excluding technical details that are important only for node maintaining.
  
Statistics will be collected by analyzing regular requests to API server. And will be stored for each Sugar Network node. It will be  possible to get direct access to this stats using node's [[Pjlatform_Team/Sugar_Network/API|API]]. Besides, slave node statistics will be collected on a master node.
+
Statistics will be collected by analyzing regular requests to API server. And will be stored for each Sugar Network node. It will be  possible to get direct access to this stats using node's [[Platform_Team/Sugar_Network/API|API]]. Besides, slave node statistics will be collected on a master node.
  
 
== Common statistics ==
 
== Common statistics ==

Revision as of 02:28, 26 October 2012

Summary

This page describes what kind of statistics Sugar Network node servers generate. Statistics is about the entire node server and not personalized. Besides, statistics is being targeted to edu researchers rather than service maintainers, i.e., excluding technical details that are important only for node maintaining.

Statistics will be collected by analyzing regular requests to API server. And will be stored for each Sugar Network node. It will be possible to get direct access to this stats using node's API. Besides, slave node statistics will be collected on a master node.

Common statistics

  • user
    • user.total
      Total number of existing objects.
    • user.created
      Number of created objects.
    • user.deleted
      Number of deleted objects.
    • user.active
      Number of unique users that take part in regular server interactions, i.e., authenticated and subscribed to server events.
    • user.hits
      Number of direct object accesses.
  • context
    • context.total
      Total number of existing objects.
    • context.activities
      Number of Sugar activities among context.total.
    • context.content
      Number of content among context.total.
    • context.projects
      Number of projects among context.total.
    • context.created
      Number of created objects.
    • context.deleted
      Number of deleted objects.
    • context.active
      Number of unique objects involved, directly or indirectly, in users' interactions.
    • context.hits
      Number of direct object accesses.
    • context.updated
      Number of newly uploaded Implementations with new versions.
    • context.failed
      Number of newly uploaded fail Reports.
    • context.downloaded
      Number of Implementation downloads.
  • review
    • review.total
      Total number of existing objects.
    • review.created
      Number of created objects.
    • review.deleted
      Number of deleted objects.
    • review.active
      Number of unique objects involved, directly or indirectly, in users' interactions.
    • review.hits
      Number of direct object accesses.
  • feedback
    • feedback.total
      Total number of existing objects.
    • feedback.ideas
      Number of ideas among feedback.total.
    • feedback.problems
      Number of problems among feedback.total.
    • feedback.questions
      Number of questions among feedback.total.
    • feedback.solutions
      Objects among feedback.total that have Solutions assigned.
    • feedback.created
      Number of created objects.
    • feedback.deleted
      Number of deleted objects.
    • feedback.active
      Number of unique objects involved, directly or indirectly, in users' interactions.
    • feedback.hits
      Number of direct object accesses.
    • feedback.solved
      Number of assigned Solutions.
    • feedback.rejected
      Number of rejected Solutions.
  • solution
    • solution.total
      Total number of existing objects.
    • solution.created
      Number of created objects.
    • solution.deleted
      Number of deleted objects.
    • solution.active
      Number of unique objects involved, directly or indirectly, in users' interactions.
    • solution.hits
      Number of direct object accesses.
  • artifact
    • artifact.total
      Total number of existing objects.
    • artifact.created
      Number of created objects.
    • artifact.deleted
      Number of deleted objects.
    • artifact.active
      Number of unique objects involved, directly or indirectly, in users' interactions.
    • artifact.hits
      Number of direct object accesses.
    • artifact.downloaded
      Number of downloads.
  • comment
    • comment.total
      Total number of existing objects.
    • comment.created
      Number of created objects.
    • comment.deleted
      Number of deleted objects.
    • comment.hits
      Number of direct object accesses.

Per object statistics

While calculating common statistics, node will generate per object sums as well (still not personalized).

These are Sugar Network objects that will be affected:

  • Context properties:
    • Context.downloads
      Number of total downloads for the Context.
    • Context.rating
      Average rating given to the Context while reviewing.
  • Artifact properties:
    • Artifact.downloads
      Number of total downloads for the Artifact.
    • Artifact.rating
      Average rating given to the Artifact while reviewing.

Getting involved

  • Submit your bug report or feature request.
  • Browse our implementation discussions, and post your feedback. (You should join this discussion list in order to avoid having your messages postponed for moderation.)