Follow-up to #9187
The validation of the Bigeye configs is currently not reliable due to different casing of the predefined_metric names (always uppercase) and the metric_name (generally lowercase, but not always), saved_metric_id (always lowercase). The find_bigeye_checks check checks whether metrics with name volume and freshness exist across theseidentifiers. This is unreliable and has caused some issues where a saved_metric_id was wrongly set using uppercase, but the check still passing.
We should update the check to prevent this from happening.
┆Issue is synchronized with this Jira Task
Follow-up to #9187
The validation of the Bigeye configs is currently not reliable due to different casing of the
predefined_metricnames (always uppercase) and themetric_name(generally lowercase, but not always),saved_metric_id(always lowercase). Thefind_bigeye_checkscheck checks whether metrics with name volume and freshness exist across theseidentifiers. This is unreliable and has caused some issues where asaved_metric_idwas wrongly set using uppercase, but the check still passing.We should update the check to prevent this from happening.
┆Issue is synchronized with this Jira Task