Upcoming changes to "field_health" property in Monitors as Code and API

Last year, we released a big set of improvements to the Metric monitor that improved anomaly detection and the user experience on the Alert page. As part of this, we released a new metric property in Monitors as Code and the API.

Users have still been able to create monitors under the old “field_health” property, though its use to create new monitors has dwindled.

As of March 1, 2025:

• Users will no longer be able to create new monitors using the field_health property. Existing monitors using that property will continue to function without interruption and will still be editable. When creating new Metric monitors, users should use the metric property instead. The differences between the field_health and metric properties are modest, and a guide for how to navigate the two is here.
• 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. Existing monitors will continue to function without interruption.