Product improvement metrics
Overview
As of version 1.38.0, Matillion ETL comes with Product Improvement Metrics, a system that can gather data seamlessly in the background of the application.
To see this dialog, click Admin → Product Improvement Metrics.
This metadata, if enabled, will be periodically reported to Matillion and is critical to Matillion understanding how Matillion ETL is used, and by extension 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 dialog prompt.
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.
System information
Purpose: To help Matillion understand its active installations.
Fields collected:
- Instance IDs (Hashed account/instance IDs).
- Platform & database.
- Timestamp.
- Version.
- Persistence (for example, mongo, postgres-{hashed_url}).
- License Key Limits (if applicable).
- Socket limits.
- Environment limits.
- Feature flags.
- License Key Hash code.
- Instance Type/Size.
- Uploaded JDBC Drivers.
- Memory Usage.
- Out-of-memory error counts.
- User count.
Command usage
Purpose: To help Matillion understand which client and server functions are being called.
Fields collected:
- Instance IDs (Hashed account/instance IDs).
- Platform & database.
- Persistence (for example, mongo, postgres-{hashed_url}).
- Timestamp.
- Version.
- The class name of the function implementation.
- The number of times that function was called within the collection period.
No metadata associated with the command is collected or sent, only the number of occurrences.
Component usage
Purpose: To help Matillion understand which components are being used, and their efficiency.
Fields collected:
- 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.