Skip to content

maint: Update release status metrics

Jenny Kim requested to merge jennykim/update-monthly-release-status-metric into master

What does this MR do and why?

We currently only emit the delivery_release_monthly_status and delivery_release_patch_status metrics during steps of the respective release, so the "Delivery: Release Information" Grafana dashboard currently has to have a pretty big time range to go back in time to look for the latest one that was emitted.

For example, we create the metric delivery_release_monthly_status for the next monthly version when we finalize the previous monthly release version, and the next time the metric gets created is in 3-4 weeks, when we announce the guaranteed sha.

The problem is that once the metrics are created, the metric only lasts for a few days on grafana, and gets flushed when the deployment gets re-deployed. So we need a mechanism to keep recreating (refreshing) the metrics for it to appear on grafana.

This change refreshes/updates the metric so that the latest information for the current version will persist on grafana, alongside when other pressure metrics get updated in our scheduled pipelines. (This problem also exists with those pressure metrics, so we're piggyback-ing off of that)

I'll create a follow-up MR for reducing the time range, once we have confirmed that this works in persisting the metric on grafana.

Related: gitlab-com/gl-infra/delivery#20181 (comment 1889107698)

Feature flag in release/tools: release_status_metric

Prior to merging

After merging

  • Create a follow-up MR to reduce the time range on the dashboard
Edited by Jenny Kim

Merge request reports

Loading