- "automates root cause analysis" -> it means (1) showing which rows have affected the metrics and (2) provide some automated context (is it an update? a delete? a dimension that changed? etc). But it is still very early for 2.
- Metrics are defined by users in their usual "data" repository (using dbt for example). The metric computation is not defined on Datadrift, we only go "read it".
- No, it's really for batch processing in a data warehouse (like hourly / daily computations)
- That's not something we had in mind (I know some dbt package can help you do this)
Comments
thanks for the feedback!
- "automates root cause analysis" -> it means (1) showing which rows have affected the metrics and (2) provide some automated context (is it an update? a delete? a dimension that changed? etc). But it is still very early for 2.
- Metrics are defined by users in their usual "data" repository (using dbt for example). The metric computation is not defined on Datadrift, we only go "read it".
- No, it's really for batch processing in a data warehouse (like hourly / daily computations)
- That's not something we had in mind (I know some dbt package can help you do this)