NEWS, 29 OCT 2026, read 13 Nov 2026
Databricks makes data quality monitoring anomaly detection generally available
Databricks marked anomaly detection for data quality monitoring as generally available in its product release notes dated 29 Oct 2026. The feature is switched on per schema rather than per table.
Per Databricks, once enabled it monitors the freshness and completeness of every table in the schema, based on historical data patterns instead of thresholds a person sets by hand. Results for all monitored tables are written to the system.data_quality_monitoring.table_results system table, which Databricks says is also generally available as of the same date.
For a head of data with thousands of tables, a queryable results table is the part that matters. A readiness rule can read from it: a table whose last freshness or completeness check failed does not get the label. Databricks describes only freshness and completeness here, so ownership, documentation and certification still need their own checks.
More readiness news
- Monte Carlo adds an Analytics API that reports data health through its MCP server4 Nov 2026
- Qlik introduces Semantic Models for data products and plans MCP tool support28 Oct 2026
- DataHub 1.8.0 nests data products and adds a Monte Carlo ingestion source22 Oct 2026
- OpenMetadata 2.0.6 fixes data quality runs that reported success without finishing21 Oct 2026
Sources
- docs.databricks.com/aws/en/release-notes/product/, read 13 Nov 2026
Last reviewed 13 Nov 2026.