Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

Version 1 Next »

Introduction

There are many reasons to collect usage statistics, for example:

  • It can help in improving the product in the main used areas and features (steps, job entries, database types etc.)
  • It can help the user to determine if some features are effected by a planned upgrade (the upgrade notes on each release cover affected steps, job entries etc.)
  • When it gets combined with usage statistics in development/test/production you can also determine if some jobs/transformation are never used

Solutions

Analyze the used steps, job entries and database types

  1. Download the solution _analyze_trans_job
  2. Within PDI/Kettle, please open the job _analyze_trans_job/transformations_jobs/0_analyze_trans_job.kjb
  3. Look at the comment within the job, it gives you all the usage information.
  4. The sending of the results to the given address is absolutely anonymous and you can opt-in with your personal data if you like.

If you want to contribute to this solution, the jobs/transformations are hosted at GitHub:

Pentaho Operations Mart

Within the PDI Enterprise Edition, the Pentaho Operations Mart collects a lot of information and also usage statistics. These can be combined to see what jobs/transformations etc. are used, how often, from what user, .

  • No labels