[
https://jira.jboss.org/browse/JBIDE-6376?page=com.atlassian.jira.plugin.s...
]
Andre Dietisheim edited comment on JBIDE-6376 at 8/19/10 10:11 AM:
-------------------------------------------------------------------
Max proposed a global 'kill switch' that allows us to disable stats. In other
words the plugin would not trigger any stats even if the (user settable) eclipse
preferences tells it to do so.
We would implement that with a page or WS that the plugin queries and determines if stats
are globally on/off.
IMHO this could be achieved if we pinged (requested) to an internal URL that forwards to
google analytics. We wouldn't need any additional HTTP Request. Any ideas?
was (Author: adietish):
max proposed a global 'kill switch' that shall allow us to disable stats.
IMHO this could be achieved if we pinged (requested) to an internal URL that forwards to
google analytics. We wouldn't need any additional HTTP Request. Any ideas?
Usage tracking of JBoss tools
-----------------------------
Key: JBIDE-6376
URL:
https://jira.jboss.org/browse/JBIDE-6376
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: core
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.2.0.M2
Attachments: GoogleAnalyticsAndroid_0.7.zip
We would like to know how many actually use jboss tools.
We got some data from eclipse update sites but they are unreliable.
Better if we could do a simple ping to a server to track when eclipse is started with
JBoss Tools.
Default will be on, but should be easy to disable.
Default should not track more than what a visit to a webpage tracks.
Suggestion is to use Google Analytics to track it.
jgoogleanalytics could be a good basis for this.
http://code.google.com/p/jgoogleanalytics/
Other requirements:
Should not ping more than once a day (per workspace or per eclipse instance ?, per
workspace I would say)
Should be done asynchronosuly to not have any UI delays
Should have some way to anonymously track users so we don't skew the usage data
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira