Repository navigation
Add Comprehensive Guide to Snowflake Data Quality Monitoring - #3506
Closed
sfc-gh-yostrinsky wants to merge 2 commits into
Closed
sfc-gh-yostrinsky wants to merge 2 commits into
sfc-gh-yostrinsky wants to merge 2 commits into
Conversation
Example-led guide: a small shared setup plus self-contained recipes, so a reader can run any single example without working through the others. Part 1 only (overview, setup, profiling, anatomy of a check). All SQL verified against a live account; result tables are real output. Covers two behaviours that are easy to get wrong: time-relative metrics reject TIMESTAMP_NTZ, and UNSET DATA_METRIC_SCHEDULE reverts to the default hourly cadence rather than suspending monitoring. .... Generated with [Cortex Code](https://docs.snowflake.com/en/user-guide/cortex-code/cortex-code) Co-Authored-By: Cortex Code <noreply@snowflake.com>
Adds the metric catalogue and decision table, twelve failure-mode recipes, custom metrics, schema-wide monitoring, AI-suggested checks, anomaly detection, remediation, notifications, the circuit breaker, layer strategy, quality as code, cost and cleanup. Every SQL block runs against a live account and the result tables are real output. Findings worth noting in the prose: - FRESHNESS can return a negative value when a future-dated row is the newest timestamp, so a freshness check alone can be defeated by one bad timestamp. Paired with the clock-skew check. - SYSTEM$EVALUATE_DATA_QUALITY_EXPECTATIONS does not record its result; the _PERSIST_RESULT variant does. Anything reading monitoring history needs the latter. - The circuit breaker uses an ALERT because the native notification settings have no action hook. Proven end to end: alert TRIGGERED and the downstream task suspended. .... Generated with [Cortex Code](https://docs.snowflake.com/en/user-guide/cortex-code/cortex-code) Co-Authored-By: Cortex Code <noreply@snowflake.com>
sfc-gh-yostrinsky
force-pushed
the
dq-monitoring-comprehensive-guide
branch
from
September 18, 2026 08:56
547e512 to
7008610
Compare
Collaborator
Author
|
Superseded by #3542 — moved from a fork branch to a branch in this repository so the staging preview workflow can run, and rebased onto current master. Preview is live there. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A new example-led guide to Data Quality Monitoring. Draft, opened for review.
DQ_EXAMPLES) with seven deliberately seeded defects, each named openly so every check is verifiable.Provenance
Every SQL block was run against a live Enterprise account and the result tables are real output, not illustrative. Three behaviours the guide calls out because they were found by running it:
FRESHNESScan return a negative value when a future-dated row is the newest timestamp, so a freshness check alone can be defeated by one bad timestamp. The guide pairs it with the clock-skew check.SYSTEM$EVALUATE_DATA_QUALITY_EXPECTATIONSdoes not record its result; the_PERSIST_RESULTvariant does. Anything reading monitoring history needs the latter.UNSET DATA_METRIC_SCHEDULEreverts to the default hourly cadence rather than suspending monitoring. The suspend isSET DATA_METRIC_SCHEDULE = ''.The circuit breaker was proven end to end (alert
TRIGGERED, downstream task suspended), and uses anALERTobject because the native notification settings have no action hook.Known gaps before this leaves draft
TODO: screenshotplaceholders mark what each image must showTest plan