TIBCO Jaspersoft® Studio Usage Reporting

Overview

Since April 2015, TIBCO Jaspersoft® Studio has provided 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 sensitive information like passwords, usernames or URLs

What will we use the data for

With this utility enabled, we can start seeing better how and where TIBCO Jaspersoft Studio is being used. We are especially interested in:

  • which type of templates are the most used
  • how many users integrate with TIBCO JasperReports® Server
  • which exporters are frequently used

This will help guide decisions in the future, such as what resources to put towards which improvements.

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 first start, a dialog will pop up asking you for permission to send anonymous usage statistics.

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

If you later decide to not send statistics, 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 adapters are used
  • Which types of reports are used (Normal, Interactive, Book, KPI)
  • Which exporters are used
  • How many connections to JasperReports Server were created

This data contains information about the use of specific objects, but not their configuration information. For example, a statistic might record that a JDBC data adapter was created 5 times, but it will not contain any information about the data adaper itself. Users will not experience any significant impact on performance. The upload of the statistics is done through a dedicated eclipse job. We also generate a random id for the installation so multiple startups from the same eclipse only count as one usage.  

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.

Feedback