Incidents Overview
Derive insights on your data quality by our metrics.
Last updated
Derive insights on your data quality by our metrics.
Last updated
The Data Quality section provides a comprehensive view of all data quality incidents reported within a specified timeframe. These incidents are categorized under:
Freshness
Volume
Field Health
Schema Drift
Custom SQL
Job Failure
For each incident, detailed information is provided, including the affected table/column and the timestamp when the incident was identified.
A new column for Test Name was added, and a single Incident Type column was created by merging, Incident Type, Test Type, and Monitor Mode.
By selecting any incident from the Data Quality module, users will be redirected to the Incident Details page. This page provides you with a deeper understanding of and historical trend of the chosen incident.
On the Incident Details page, you can add an Assignee to the selected incident. All such actions will subsequently be logged and can be reviewed in the Audit History section on the bottom right.
When an incident is raised, it creates an open incident. You can choose to either:
close an incident.
mute it for a period of time. This ensures you don't get alerts when another incident is triggered on the same table/column. Incidents are automatically unmuted after the time period you have set.
In the History tab, a list of past tests is shown, including the metrics of successful scans. This is a quick way to identify the scans that had failed along with the values that had caused the failed tests.
Based on the downstream lineage, a list of impacted assets is able to be generated to show to the user the potential downstream tables or jobs or dashboards that may be affected by the incident. Users can then opt to export this list as a csv and send them to the respective owners that were designated in the Catalog.
