OBSERVABILITY Signal 98
Custom labels in Grafana Cloud Synthetic Monitoring: New updates for consistency and ease-of-use
↗
Illustration only Photo by Taylor Vick on Unsplash
Labels provide a way to organize telemetry and define policies across Grafana Cloud, while Synthetic Monitoring custom labels were previously limited to the sm_check_info metric and now receive updates for consistency and ease-of-use.
Engineers can now apply custom labels in Synthetic Monitoring with the same consistency they expect from other Grafana Cloud components. This reduces the need for work-arounds that were required when labels lived only on the sm_check_info metric, simplifying alerting and access control setup.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
The update concerns custom labels in Grafana Cloud Synthetic Monitoring.
Previously, these custom labels were confined to the single sm_check_info metric.
The changes aim to improve consistency and ease-of-use for those labels.
THE READ
What the cluster adds up to.
The update concerns custom labels in Grafana Cloud Synthetic Monitoring, aiming for consistency and ease-of-use. Previously, these labels were limited to the sm_check_info metric. The update changes that behavior to be more consistent with label usage elsewhere in Grafana Cloud. This means engineers can now apply custom labels in Synthetic Monitoring with similar expectations as other components.
The material does not specify any additional cost or effort required to adopt the update. Engineers can continue using their existing Synthetic Monitoring checks while benefiting from the improved label consistency. No new infrastructure or licensing changes are mentioned. The update appears to be a service-side change that does not require client-side modifications.
The update is described only for Synthetic Monitoring within Grafana Cloud; the material does not mention any effect on other data sources or external systems. Therefore, label handling for other parts of the observability stack remains as before. If users have workflows that depended on the previous single-metric label behavior, they may need to review those workflows. The material does not provide details on any limitations of the update itself.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER