Data Quality & Observability
Automated Data Quality and Observability: Glossary & Technical Reference
A
Accuracy
The degree to which a data value correctly represents the real-world fact it is intended to represent. Accuracy is one of the core data quality dimensions.
Anomaly Detection
The process of identifying unusual patterns or behavior in data, pipelines, or observed metrics that deviate from established historical expectations.
Automated Data Quality
The use of automated rules, statistical checks, and validation processes to evaluate data against defined quality expectations without relying on manual inspection.
B
Baseline
A representation of normal historical behavior used to determine whether a data quality metric or pipeline observability metric has changed significantly.
Blast Radius
The set of downstream reports, dashboards, systems, or processes affected by an upstream data quality issue or observability failure, typically identified through lineage.
C
Completeness
A data quality dimension that measures whether required data is present and expected fields or records are populated.
Consistency
A data quality dimension that measures whether data agrees across records, fields, systems, or defined business expectations.
D
Data Distribution
The statistical pattern of values within a data set. Monitoring distribution changes can reveal unusual shifts even when individual values remain technically valid.
Data Lineage
The traceable path showing where data originates, how it moves or changes, and which downstream assets depend on it.
Data Observability
The practice of continuously monitoring the health and behavior of data pipelines using signals such as freshness, volume, schema, distribution, and lineage.
Data Quality
The degree to which data meets defined expectations for characteristics such as completeness, accuracy, validity, consistency, and uniqueness.
Data Quality Automation
The automated execution of data validation, quality rules, profiling, monitoring, and exception handling to identify quality issues with minimal manual intervention.
Data Quality Rule
A defined condition used to evaluate whether data meets an expected quality standard, such as a required field being populated or a value remaining within an approved range.
Data Quality Score
An aggregate measure representing how well a data set conforms to its defined quality rules over time.
Data Quality & Observability
A connected discipline combining value-level data quality checks with continuous monitoring of the pipelines and structures delivering that data.
Data Downtime
A period during which a data pipeline or data product is missing, delayed, incomplete, or otherwise unreliable for its intended use.
F
Freshness
An observability dimension that measures whether data is being updated or delivered according to its expected schedule.
L
Lineage Mapping
The process of mapping dependencies from source data through transformations and pipelines to downstream reports, dashboards, or systems.
P
Pipeline Health
The operational condition of a data pipeline based on indicators such as freshness, volume, successful execution, schema stability, and other monitored signals.
Pipeline Monitoring
The continuous observation of data pipeline behavior to identify delays, failures, unexpected volume changes, or other operational anomalies.
Q
Quality Rule Engine
The component responsible for executing defined data quality rules and identifying records or data sets that violate those rules.
S
Schema Drift
An unexpected or unmanaged change in the structure of a data source or downstream table, such as a new column, removed field, or changed data type.
Schema Monitoring
The continuous or scheduled process of checking data structures for unexpected changes that could affect pipelines or downstream consumers.
U
Uniqueness
A data quality dimension that measures whether records or values that should be unique are duplicated.
V
Validity
A data quality dimension that measures whether values conform to defined formats, ranges, types, or business rules.
Volume Monitoring
An observability practice that tracks whether the amount of data arriving in a pipeline is consistent with expected historical or defined levels.
Core Observability Dimensions
Freshness
Whether data arrives or updates on the expected schedule.
Volume
Whether the expected quantity of records or data is being delivered.
Schema
Whether the structure of the data remains as expected.
Distribution
Whether statistical patterns in the data remain within expected behavior.
Lineage
Whether the dependencies and movement of data from source to downstream consumers remain traceable.
Core Data Quality Dimensions
Completeness
Whether required data is present.
Accuracy
Whether values correctly represent the facts they are intended to represent.
Validity
Whether values conform to defined rules, formats, and ranges.
Consistency
Whether data agrees with defined expectations across records or systems.
Uniqueness
Whether records or values that should be unique are free from unintended duplication.
Key Acronyms
| Acronym | Meaning |
| API | Application Programming Interface |
| ETL | Extract, Transform, Load |
| IoT | Internet of Things |
| ERP | Enterprise Resource Planning |
| SLA | Service Level Agreement |
| SQL | Structured Query Language |
See Data Quality & Observability in 4DAlert
Explore how 4DAlert implements the concepts in this guide as a working platform.