TIBCO Jaspersoft® Studio Usage Reporting


Since April 2015,  TIBCO Jaspersoft® Studio provide a "Usage Manager" utility which when installed and enabled will help us gather anonymous statistics about how the application is being used. All the data is gathered anonymously and can at any time be disabled if you wish. This data doesn't contains any sensible information like password, usernames, URL and so on.

What will we use the data for

With this enabled we can start seeing better how and where TIBCO Jaspersoft Studio is being used; we are especially currently interested in which are the type of templates are the most used, how many users integrate with TIBCO JasperReports® Server and which exporters are frequently used. This will help guide decisions in the future, such as how much resources put in the improvments of the existing resources.

How to enable/disable the usage tracking

Over time we hope to learn more to help continuously improve Jaspersoft Studio. If you have done a new installation of Jaspersoft Studio, then on the first start of this Eclipse a dialog will pop up asking you to send anonymous usage statistics.

If you do not want to send anonymous usage statistics, press the button No. If you press Yes then usage statistics for Jaspersoft Studio is enabled.

If you later on decide to not send statistics anymore or want to enable it, simply goto the Preferences -> Jaspersoft Studio.

How it works

When the user has enabled reporting anonymous statistics the number of time some functions are used is stored. The tracked functions are:

  • Which types of data adapter are used
  • Which types of report are used (Normal, Interactive, Book, KPI)
  • Which exporters are used
  • How many connections to JasperReports Server were created

All the collected data regards only the amount of a specific use of an object but dosen't contains any information on its configuration. For example a statistic can contains that a JDBC data adapter was created 5 times, but it will not contains any information about the data adaper itself.

The upload of the statistics is at least after a week after the previous one and both the uploads and the track of the statistics is done trough a dedicated eclipse Job. Doing this there is no sensible impact on the performances from the point of view of the user. We also generate a random id for the installation so multiple startups from the same eclipse only count as one usage.  We might add more reporting in the future, if so this page will be updated with details.

If you want to inspect the source code for all of the above it can be found here. If you have any problems to access to SVN server or checkout the code please check also this tutorial.