-
Notifications
You must be signed in to change notification settings - Fork 124
feat(DENG-9188) Add BigConfig checks to targeted stable tables #8436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
This comment has been minimized.
This comment has been minimized.
Integration report for "Update README.md"
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The SQL generator could be renamed to something like stable_table_monitoring to make it clearer that it is generating monitoring related configs
| @@ -0,0 +1,12 @@ | |||
| friendly_name: Stable Table BigEye Checks | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the friendly name should match that of the related stable table
|
Two things that may need to be taken into account:
|
Description
This PR adds the feature to add BigConfig monitoring checks (freshness and volume) to a targeted set of stable tables.
Approach - apply this change to an asset that is currently not in use
This PR will create the metadata and bigconfig yaml files for
moz-fx-data-shared-prod.mozilla_vpn_external.waitlist_v1. This table has not been queried in the last 6 months and does not have any downstream tables or Looker Explores.Output:

TODO:
Confirm if this may impact other configurations in BigQuery unexpectedly.
Related Tickets & Documents
Reviewer, please follow this checklist