Data Monitoring / Pipeline Freshness & Data Quality
Data pipelines: Lineage-aware incident scope
A source defect is corrected but dependent reports remain stale. Trace downstream tables, semantic models and dashboards from the affected dataset.
Environment and inputs: Data pipelines and analytical datasets; Apache Airflow is an orchestration example. Quality acceptance rules must match the dataset contract.
Failure scenario
A source defect is corrected but dependent reports remain stale. Confirm the cause before choosing a fix.
Evidence to collect
Trace downstream tables, semantic models and dashboards from the affected dataset. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Rebuild or refresh the impacted dependencies in the right order and verify their business watermarks. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for lineage-aware incident scope using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.
Scope and precautions
Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.