Product Improvement Metrics

As of version 1.38.0, Matillion ETL comes with Product Improvement Metrics, a system that can gather anonymized data seamlessly in the background of the client. This data, if enabled, will be periodically reported to Matillion and is key to us understanding how Matillion ETL is used and thus how to build a better product in the future.

Upon upgrading, admins will be prompted to opt in or out of Product Improvement Metrics for their instance by checking the box in the below dialog.


This dialog will only appear once per instance. This dialog can be revisited at any time by an Admin via Admin → Product Improvement Metrics.


The below table describes all of the data that Matillion ETL collects from the client as part of the Product Improvement Metrics. No personal or identifying data is collected in any circumstance.

Record Type

Purpose

Fields Collected

System Information

To help Matillion understand it’s active installations.

  • Instance IDs (Hashed account/instance IDs)
  • Platform & database
  • Timestamp
  • Version
  • Persistence (e.g. mongo, postgres-{hashed_url})
  • ​License Key Limits (if applicable)
  • Socket limits
  • Environment limits
  • Feature flags
  • License Key Hashcode
  • Instance Type/Size
  • Uploaded JDBC Drivers
  • Memory Usage
  • Out-of-memory Error Counts
  • User count

Command Usage

To help Matillion understand which client and server functions are being called

  • Instance IDs (Hashed account/instance IDs)
  • Platform & database
  • Persistence (e.g. mongo, postgres-{hashed_url})
  • Timestamp
  • Version
  • The classname of the function implementation
  • ​The number of times that function was called within the collection period
 

No data associated with the command is collected or sent, simply the number of occurrences.

Component Usage

To help Matillion understand which components are being used and their efficiency.

  • Instance IDs (Hashed account/instance IDs).
  • Platform & database
  • Persistence (e.g. mongo, postgres-{hashed_url})
  • Timestamp
  • Version
  • Component Implementation ID
  • Outcome (success/failure)
  • Time taken and Rows processed (if applicable)
  • Task batch method (Run Transformation, API, Queue, etc)
  • Task Batch id
  • ​Row count
 

No component configuration (parameter values) information is collected or sent.