diff --git a/docs/data-sources/athena.md b/docs/data-sources/athena.md index c8d1bf14b0..9bdfcdf3dd 100644 --- a/docs/data-sources/athena.md +++ b/docs/data-sources/athena.md @@ -97,8 +97,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/aws.md b/docs/data-sources/aws.md index 87f7c83550..58dc1d1739 100644 --- a/docs/data-sources/aws.md +++ b/docs/data-sources/aws.md @@ -220,8 +220,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/azure.md b/docs/data-sources/azure.md index 4deb8ccb1d..fbb1ac675d 100644 --- a/docs/data-sources/azure.md +++ b/docs/data-sources/azure.md @@ -249,8 +249,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/bigquery.md b/docs/data-sources/bigquery.md index 1fce487bc3..a5dc678a80 100644 --- a/docs/data-sources/bigquery.md +++ b/docs/data-sources/bigquery.md @@ -77,8 +77,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/clickhouse.md b/docs/data-sources/clickhouse.md index a04cbacc9a..fa1b149c8c 100644 --- a/docs/data-sources/clickhouse.md +++ b/docs/data-sources/clickhouse.md @@ -87,8 +87,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/csv.md b/docs/data-sources/csv.md index b72e8e31a1..0ac2265b5d 100644 --- a/docs/data-sources/csv.md +++ b/docs/data-sources/csv.md @@ -185,8 +185,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/databricks.md b/docs/data-sources/databricks.md index 41d6f49014..a482c3ba45 100644 --- a/docs/data-sources/databricks.md +++ b/docs/data-sources/databricks.md @@ -97,8 +97,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/db2.md b/docs/data-sources/db2.md index e30d63bb2c..7e8fba0d87 100644 --- a/docs/data-sources/db2.md +++ b/docs/data-sources/db2.md @@ -89,8 +89,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/deltalake.md b/docs/data-sources/deltalake.md index bc5c093f96..e5e8aab16c 100644 --- a/docs/data-sources/deltalake.md +++ b/docs/data-sources/deltalake.md @@ -134,8 +134,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/gcp.md b/docs/data-sources/gcp.md index 7e74bb2ce7..7e7bf37b95 100644 --- a/docs/data-sources/gcp.md +++ b/docs/data-sources/gcp.md @@ -125,8 +125,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/hana.md b/docs/data-sources/hana.md index 699aa5f10c..d2e5abf2dd 100644 --- a/docs/data-sources/hana.md +++ b/docs/data-sources/hana.md @@ -88,8 +88,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/iceberg.md b/docs/data-sources/iceberg.md index de9a35816d..00baee1ee2 100644 --- a/docs/data-sources/iceberg.md +++ b/docs/data-sources/iceberg.md @@ -149,8 +149,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/json.md b/docs/data-sources/json.md index b9a408d5be..79e6f93d53 100644 --- a/docs/data-sources/json.md +++ b/docs/data-sources/json.md @@ -182,8 +182,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/mariadb.md b/docs/data-sources/mariadb.md index 05fbea5565..5553b6dc9f 100644 --- a/docs/data-sources/mariadb.md +++ b/docs/data-sources/mariadb.md @@ -82,8 +82,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/mysql.md b/docs/data-sources/mysql.md index f5bb06dc9f..1cab037a1e 100644 --- a/docs/data-sources/mysql.md +++ b/docs/data-sources/mysql.md @@ -93,8 +93,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/oracle.md b/docs/data-sources/oracle.md index 2e974ecdfd..d4328857d2 100644 --- a/docs/data-sources/oracle.md +++ b/docs/data-sources/oracle.md @@ -79,8 +79,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/parquet.md b/docs/data-sources/parquet.md index 174bfd4a87..9dada1f492 100644 --- a/docs/data-sources/parquet.md +++ b/docs/data-sources/parquet.md @@ -171,8 +171,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/postgresql.md b/docs/data-sources/postgresql.md index 8ba5f5ce52..f3cece6b4e 100644 --- a/docs/data-sources/postgresql.md +++ b/docs/data-sources/postgresql.md @@ -89,8 +89,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/presto.md b/docs/data-sources/presto.md index b43727b75c..45cdd68044 100644 --- a/docs/data-sources/presto.md +++ b/docs/data-sources/presto.md @@ -82,8 +82,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/questdb.md b/docs/data-sources/questdb.md index 0b8b178e09..df0e720292 100644 --- a/docs/data-sources/questdb.md +++ b/docs/data-sources/questdb.md @@ -79,8 +79,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/redshift.md b/docs/data-sources/redshift.md index c1b960ab51..c101881936 100644 --- a/docs/data-sources/redshift.md +++ b/docs/data-sources/redshift.md @@ -92,8 +92,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/single-store.md b/docs/data-sources/single-store.md index ac35bb70c4..a1ed187d0a 100644 --- a/docs/data-sources/single-store.md +++ b/docs/data-sources/single-store.md @@ -86,8 +86,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/snowflake.md b/docs/data-sources/snowflake.md index f61635a9ce..c3bf6f25b7 100644 --- a/docs/data-sources/snowflake.md +++ b/docs/data-sources/snowflake.md @@ -93,8 +93,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/spark.md b/docs/data-sources/spark.md index 9fb35cb388..3f0e67fbd2 100644 --- a/docs/data-sources/spark.md +++ b/docs/data-sources/spark.md @@ -85,8 +85,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/sql-server.md b/docs/data-sources/sql-server.md index bfeeb76547..b6ae9dfb62 100644 --- a/docs/data-sources/sql-server.md +++ b/docs/data-sources/sql-server.md @@ -90,8 +90,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/teradata.md b/docs/data-sources/teradata.md index 8da1be8e28..020a4bdb4c 100644 --- a/docs/data-sources/teradata.md +++ b/docs/data-sources/teradata.md @@ -87,8 +87,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/timescale.md b/docs/data-sources/timescale.md index fe336d0133..a1bbacb55e 100644 --- a/docs/data-sources/timescale.md +++ b/docs/data-sources/timescale.md @@ -79,8 +79,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/data-sources/trino.md b/docs/data-sources/trino.md index 5faf99fead..304b9f719d 100644 --- a/docs/data-sources/trino.md +++ b/docs/data-sources/trino.md @@ -83,8 +83,8 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" - Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md). - These checks include row count, table availability, and checks detecting schema changes. The profiling checks are scheduled + Once new tables are imported, DQOps automatically activates [profiling and monitoring checks](../dqo-concepts/definition-of-data-quality-checks/index.md) which are which are pre-enabled by [data quality policies](../dqo-concepts/data-observability.md#automatic-activation-of-checks). + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess diff --git a/docs/getting-started/add-data-source-connection.md b/docs/getting-started/add-data-source-connection.md index 6dc8a8bb4b..df70eb6477 100644 --- a/docs/getting-started/add-data-source-connection.md +++ b/docs/getting-started/add-data-source-connection.md @@ -128,7 +128,7 @@ and profiling data by running default data profiling checks. Simply click on the !!! info "Automatically activated checks" Once new tables are imported, DQOps automatically activates checks defined in [data policies](../dqo-concepts/data-observability.md) - These checks include row count, table availability, and checks detecting schema changes. By default, the profiling checks are scheduled + These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. By default, the profiling checks are scheduled to run at 1:00 a.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m. [**Profiling checks**](../dqo-concepts/definition-of-data-quality-checks/data-profiling-checks.md) are designed to assess