Schema Monitoring Overview
Audience: Data Owners and Governors
Content Summary: This page outlines the uses of schema monitoring and table evolution detection in query-backed data sources.
Schema Monitoring is enabled while creating a data source or when editing a data source. It monitors servers for schema and table changes, including when schemas and tables are added or removed, and notifies Data Owners when any changes are made.
When this feature is enabled by a Data Owner, Immuta detects when a new table has been added and automatically creates a new data source. Correspondingly, if a remote table is removed, that data source will be disabled in the console.
Data Owners or Governors can select which users will monitor schema changes, and if more than one user is selected as a monitor, one data source will be created for each of these users.
See Create Query-backed Data Source for instructions on enabling it.
Table Evolution Detection
Data Owners can also enable Table Evolution Detection, which monitors when columns are added or removed and when column types are changed.
When new columns are added to the remote table, Immuta automatically applies the
New tag to these columns in the data
source, and, since these new columns could contain sensitive data, a seeded
New Column Added Global Policy masks
Data Owners can then review and approve these changes from the Requests tab of their profile page.
Approving column changes removes the
New tags from the data source.
See Create a Query-backed Data Source for instructions on enabling Schema Monitoring.