Skip to content

Data quality checks #361

Description

@martyngigg

We are currently on the back foot if errors in the data are discovered as users spot them. We need to support more robust observability and quality checks on the pipelines. Some examples:

  • ingestion errors: What went wrong with a pipeline?
  • freshness: Indicators of how when data tables/models were last updated
  • source errors: Has a source stopped producing data unexpectedly?
  • pipeline tests (unit and data): support developers to know pipelines are correct

There is overlap with #78 but this is also a separate issue understanding the state of the data itself.

Recent examples of where this has gone wrong:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions