Bulk Table Configuration
A control panel for configuring multiple tables in your database.
You can now configure your tables' scan frequency, metric time, and notification settings without navigating into each Table Details in your database.
Walkthrough on our Bulk Table Config.
Upon loading the page, you must first select the data source you would like to configure.
You will see the below settings available for each table:
- Frequency: How often your table is inserted or updated. This informs our scanner how often to check your tables.
- Metric Time: Select a
datetimecolumn, eithercreated_atfor a frequently inserted table orupdated_atfor a frequently updated table. This informs our scanner to check the right column for the Frequency selected.- You will also be able to select a date column. However, selecting a date column will limit your scan frequency minimum to 24 hours.
For Google Big Query and Snowflake connections, selecting a metric time column is not a prerequisite to enable table-level tests.
- Monitor: Toggle this to enable Volume and Freshness tests to be run on your table for monitoring.
- Notify: Toggle this to allow us to send you alerts when incidents occur. You will need to have either Slack or email to be set up first before we can send you alerts.
Schema drift monitoring is enabled by default across your data source. You just have to let us know whether you'll like to get a notification by toggling it on for the specific table within the Asset Details view.
Toggle the monitoring and notifications for each table.
You can make selection of your metric time columns on multiple tables together by using the
Bulk select metric time option.If you made changes to your tables before using the bulk select, you will need to save your changes before proceeding.
Select the metric time columns and sort by priority.
Select the metric time columns that you would like to configure across multiple tables within the pop-up. You will be able to sort the metric time column by priority.
For example: if a table has both
created_at and updated_at, if created_at has higher priority than updated_at, the table will have created_at selected as its metric column.After applying your selection, you can review the selection in the Table Config list and make changes where necessary.
If you make a manual change to a metric time without the bulk select function, we will not overwrite your selection when you use the bulk select again.
Once you've configured your tables, head over to set up your alert notifications below:
Last modified 13d ago