Monitors as Code - Legacy Field Quality Monitor

As of August 17, 2025, all Field Quality monitors have been automatically converted into Custom SQL monitors. You can no longer create legacy Field Quality monitors, and their associated APIs have been disabled.

Monitors as Code (MaC) Usage

If you use the field_quality property for Monitors as Code, you can no longer create or edit these monitors.

To edit an existing monitor, you must first convert it to a custom_sql definition.

🚧

Important: You must use the same name as the original field_quality definition. Using a different name will delete the original monitor and create a new one.

To get the new custom_sql definition, use the following Monte Carlo CLI command to export your legacy definitions in the updated format:

montecarlo monitors export-as-latest --namespace <your namespace>

This command will export all field_quality definitions from your MaC files as custom_sql definitions, preserving their original names. Simply replace the old field_quality definitions with the newly exported custom_sql ones to complete the migration.

Warehouses with Data Sampling Disabled

If a Field Quality monitor was created in a warehouse where data sampling is disabled, the new Custom SQL monitor cannot be edited.

This is because the migrated monitor uses a value-based threshold, which is not supported in environments without data sampling. To make changes, you must copy the monitor and recreate it as a Metric Monitor.