[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=12948422#comment-12948422 ] 

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

Currently the work happening here will make it possible for us to add events that will report things in form of:

category, action, label, value

we plan on having 
category = component name
action = limited set of action types that can be reused across category/components(i.e. "new" will mean new artifact)
label = specific value (ie. type of action, i.e. which server type was created by new server
value = depend on context, but typically 1 = success 0 = failure or a value indicating number of times it will happen.

We would have direct events that happens on the fly to collect things like:

Which servers are a user creating succesfully:
example: ("server", "new", "org.jboss.tools.server.wtp_wildfly_8", 1)

which connector ids have been installed with success or failure
example: ("central", "install", "org.blah.egit", 1)   (0 at end would mean failure)

These should be events that are "rare" so not for everytime you publish, but okey for everytime you create a server.

Other events would be collected through the day and only sent once a day or at startup time.
have a user used visual page editor
example: ("vpe", "editor", "<type>", 23)   the 23 value here should be the number of times it was done since last report.
 
have a user used forge wizard
example: ("forge", "wizard", "<type>", 42)   the 42 value here should be the number of times it was done since last report.

have a user used forge console:
example: ("forge", "console", "<type>", 42)   the 42 value here should be the number of times it was done since last report.

This would be more often and something we would like to avoid sending all the time.

                
> 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: Alexey Kazakov
>            Priority: Critical
>              Labels: QE_JBDS80_needinfo
>
> 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