Last updated: July 22, 2025
Sensors/table
This is a list of table sensors in DQOps broken down by category and a brief description of what they do.
accuracy
Sensor name |
Description |
total_row_count_match_percent |
Table level sensor that calculates the percentage of the difference of the total row count of all rows in the tested table and the total row count of the other (reference) table. |
availability
Sensor name |
Description |
table_availability |
Table availability sensor runs a simple table scan query to detect if the table is queryable. This sensor returns 0.0 when no failure was detected or 1.0 when a failure was detected. |
custom_sql
Sensor name |
Description |
import_custom_result |
Table level sensor that uses a custom SQL SELECT statement to retrieve a result of running a custom data quality check that was hardcoded in the data pipeline, and the result was stored in a separate table. The SQL query that is configured in this external data quality results importer must be a complete SELECT statement that queries a dedicated table (created by the data engineers) that stores the results of custom data quality checks. |
sql_aggregated_expression |
Table level sensor that executes a given SQL expression on a table. |
sql_condition_failed_count |
Table level sensor that uses a custom SQL condition (an SQL expression that returns a boolean value) to count rows that do not meet the condition. |
sql_condition_failed_percent |
Table level sensor that uses a custom SQL condition (an SQL expression that returns a boolean value) to count the percentage of rows that do not meet the condition. |
sql_condition_passed_count |
Table level sensor that uses a custom SQL condition (an SQL expression that returns a boolean value) to count rows that meet the condition. |
sql_condition_passed_percent |
Table level sensor that uses a custom SQL condition (an SQL expression that returns a boolean value) to count the percentage of rows that meet the condition. |
sql_invalid_record_count |
Table level sensor that uses a custom SQL query to count rows of invalid values. |
schema
Sensor name |
Description |
column_count |
Table schema data quality sensor that reads the metadata from a monitored data source and counts the number of columns. |
column_list_ordered_hash |
Table schema data quality sensor detects if the list and order of columns have changed on the table. The sensor calculates a hash of the list of column names. The hash value depends on the names of the columns and the order of the columns. |
column_list_unordered_hash |
Table schema data quality sensor detects if the list of columns have changed on the table. The sensor calculates a hash of the list of column names. The hash value depends on the names of the columns, but not on the order of columns. |
column_types_hash |
Table schema data quality sensor detects if the list of columns has changed or any of the column has a new data type, length, scale, precision or nullability. The sensor calculates a hash of the list of column names and all components of the column's type (the type name, length, scale, precision, nullability). The hash value does not depend on the order of columns. |
timeliness
Sensor name |
Description |
data_freshness |
Table sensor that runs a query calculating maximum days since the most recent event. |
data_ingestion_delay |
Table sensor that runs a query calculating the time difference in days between the most recent transaction timestamp and the most recent data loading timestamp. |
data_staleness |
Table sensor that runs a query calculating the time difference in days between the current date and most recent data loading timestamp (staleness). |
partition_reload_lag |
Table sensor that runs a query calculating maximum difference in days between ingestion timestamp and event timestamp rows. |
uniqueness
volume
Sensor name |
Description |
row_count |
Table sensor that executes a row count query. |