[jbosstools-issues] [JBoss JIRA] (JBDS-2848) Usage Stats for actual used features

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12939557#comment-12939557 ] 

Max Rydahl Andersen commented on JBDS-2848:
-------------------------------------------

Have callback in usage that other plugins can call.
     UsageTracker ut = service.lookup(UsageTracker.class);
     ut.sendLiveEvent("org.jboss.tools.server", "create-server", "type=jboss42");  // should the last one be a map of key/values for event ?
     ut.sendDailyEvent("org.jboss.toools.browsersim", "launch-browsersim");  // only sent once
     
     Then in usage.properties (cached on startup) we can state
     event.org.jboss.tools.server.create-server=-1   // default no limit
     event.org.jboss.tools.server.create-server=0   // never send
     event.org.jboss.tools.server.create-server=5   // max 5 a day
     
     
https://developers.google.com/analytics/devguides/collection/gajs/eventTrackerGuide
Google analytics has category, action and label.
They are in a hiearchy, but analytics UI allow you to visualize at any level.
   If you have Category X and Y with action "wonka" you can see how  many "wonka"'s overall but also per category.
   
General idea:
  category = "feature/bundle" / functionality grouping (examples:  org.jboss.tools.openshift or simply openshift)
  action = name of functionallity used, i.e. "launch"  , "new-wizard", "create-server" - this names can be reused per category, but should attempt to have same conceptual meaning otherwise the reports will be misleading.
  label = optional, context of action. i.e. "jboss-4.2" for server type. "generic-eap6", "quickstart-python42", 
  value = optional, a positive integer value that we wish to track. Not sure if useful, but could be used for "number of servers configured" for server, "projects loaded on startup", etc.
Thing to consider test:
   Could we use the page title to represent an "event" so behavior flow will actually show which sequence you are working in ?
Idea: 
   liveevent could also include pages - which would allow behavior flow to be used for even more interesting understandings.

                
> Usage Stats for actual used features
> ------------------------------------
>
>                 Key: JBDS-2848
>                 URL: https://issues.jboss.org/browse/JBDS-2848
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: requirements, usage
>            Reporter: Burr Sutter
>            Assignee: Andre Dietisheim
>
> We currently know that people are using JBDS/JBoss Tools but not specifically which features people are actively using.  Our key base metric is "daily usage".
> Areas worth tracking include (in priority order):
> - Use of the OpenShift Wizard to successful completion vs error
> - Use of the archetypes on JBoss Central (adding Hybrid/Cordova in JBDS 8)
> - Successful installation of the features found on Software/Update tab of JBoss Central
> - Use of the JSF/RichFaces Visual Page Editor
> - Use of the Hibernate Tooling
> - Use of the jQuery Mobile Palette
> - Use of BrowserSim
> - Use of CordovaSim
> We will also need to update http://www.jboss.org/tools/usage and https://devstudio.jboss.com/usage/
> Ideally, we would be able to distinguish between a single "hit" (end-user opened the tool) vs active usage (end-user spent repeatedly using the tool)
> Our metric gathering service should be "scalable" enough to allow for tracking of the individual SOA features such as Drools, jBPM, Switchyard, Camel, etc in the future.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira