Great article! It is so important to repeat this again and again - sooner or later, maintaining too many metrics/insights/dashboards becomes too expensive.
We are trying to provide a tooling helping users to prevent this:
- while writing metrics, an editor should notify users about same/similar already existing metrics. Not yet in our platform, PhD thesis is progress.
- isolation/inheritance - users can create isolated workspaces. Also, they can inherit metrics from parent workspaces. We are trying to guide users to not overflow a workspace with too many metrics, instead, create separate workspace hierarchies per data product.
- lineage - being able to do an impact analysis, e.g. find impacted metrics when moving a column to a different table.
Great article! It is so important to repeat this again and again - sooner or later, maintaining too many metrics/insights/dashboards becomes too expensive.
We are trying to provide a tooling helping users to prevent this:
- while writing metrics, an editor should notify users about same/similar already existing metrics. Not yet in our platform, PhD thesis is progress.
- isolation/inheritance - users can create isolated workspaces. Also, they can inherit metrics from parent workspaces. We are trying to guide users to not overflow a workspace with too many metrics, instead, create separate workspace hierarchies per data product.
- lineage - being able to do an impact analysis, e.g. find impacted metrics when moving a column to a different table.