Sugar Network/Node Statistics

Summary

This page describes the statistics that Sugar Network node servers generate. The statistics are about the entire node server and not personalized. Note that the statistics are targeted for the interests of educational researchers rather than service maintainers, thus, technical details that are important only for node maintaining are excluded.

Statistics will be collected by analyzing regular requests to an API server and stored for each Sugar Network node. It will be possible to get direct access to these stats using node's API. In addition, slave node statistics will be uploaded to the master server.

Common statistics

Statistics will be collected per Sugar Network object type.

• 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.effective
    Number of active users that hit at least one object.
  • 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 contexts 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.contexts
    How many Context reviews among context.total.
  • review.artifacts
    How many Artifact reviews among context.total.
  • review.created
    Number of created objects.
  • review.deleted
    Number of deleted objects.
  • review.hits
    Number of direct object accesses.
  • review.commented
    Number of new comments.

• 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.hits
    Number of direct object accesses.
  • feedback.solved
    Number of assigned Solutions.
  • feedback.rejected
    Number of rejected Solutions.
  • feedback.commented
    Number of new comments.

• Solution
  
  • solution.total
    Total number of existing objects.
  • solution.created
    Number of created objects.
  • solution.deleted
    Number of deleted objects.
  • solution.hits
    Number of direct object accesses.
  • solution.commented
    Number of new comments.

• Artifact
  
  • artifact.total
    Total number of existing objects.
  • artifact.created
    Number of created objects.
  • artifact.deleted
    Number of deleted objects.
  • artifact.hits
    Number of direct object accesses.
  • artifact.downloaded
    Number of downloads.

Per object statistics

While calculating common statistics, the node will generate per object sums as well.

These are the 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.
  • Context.reviews
    Number of Reviews.

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

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.)