-
Feature Request
-
Resolution: Done
-
Critical
-
None
-
Documentation (Ref Guide, User Guide, etc.)
-
NEW
-
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.
- blocks
-
JBIDE-16800 Add usage tracking for server creation
- Closed
- is blocked by
-
JBDS-2732 Add usage tracking for installs from JBDS central
- Closed
- is related to
-
JBIDE-17520 Usage tracking for servers created via runtime detection
- Closed
- relates to
-
JBIDE-17232 Usage Stats for used wizards
- Closed
-
JBIDE-17305 Usage stats for visual page editor/preview/browsersim
- Closed
-
JBIDE-17320 Usage stats for cordovasim launches
- Closed
-
JBIDE-16906 Track successful/unsuccessful installations from JBoss Central
- Open
-
JBIDE-17260 Review what we track via usage component
- Closed
-
JBIDE-17233 Add usage tracking for the WS Tester
- Closed
-
JBIDE-17458 Usage stats for browsersim/cordovasim: webkit vs JavaFX
- Closed