Changes to legacy monitors

There are several old types of monitors that can no longer be created, because their functionality has been consolidated into the current set of monitors. Below is a list of planned changes to their functionality and/or UI, to ensure customers are benefiting from a consistent, reliable, and up to date experience.

By March 1, 2025

• Users will no longer be able to use the field_health property in Monitors as Code to create new monitors. Instead, use the metric property, to benefit from improved anomaly detection and alert UI. Existing monitors will continue to function without interruption.
• Users will no longer be able to use the createOrUpdateMonitor mutation to create a Metric monitor via the API/CLI. Customers should use createOrUpdateMetricMonitor mutation instead, to benefit from improved anomaly detection and alert UI. Existing monitors will continue to function without interruption.

By May 1, 2025

• Metrics - legacy monitors will instead appear as Custom SQL monitors in the UI. The monitors will continue to function without interruption. The substance of the notifications should remain the same, but the exact format will change to that of Custom SQL monitors.
• Dimension Tracking monitors will instead appear as Metric monitors in the UI, using the Relative Row Count metric. The monitors will continue to function without interruption. Users will benefit from improved anomaly detection and better UI, such as having thresholds visible in the charts.