From 18983956966b2ccdab2c3353010131ffb238a7e4 Mon Sep 17 00:00:00 2001 From: David Ashpole Date: Mon, 16 Dec 2024 04:42:59 -0500 Subject: [PATCH] update links to openmetrics to reference the v1.0.0 release (#5791) --- content/en/blog/2024/prometheus-compatibility-survey/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/2024/prometheus-compatibility-survey/index.md b/content/en/blog/2024/prometheus-compatibility-survey/index.md index 83a6fa8e2cca..85352faadf43 100644 --- a/content/en/blog/2024/prometheus-compatibility-survey/index.md +++ b/content/en/blog/2024/prometheus-compatibility-survey/index.md @@ -121,7 +121,7 @@ should not generally be included in the metric name. Prometheus conventions [recommend](https://prometheus.io/docs/practices/naming/#metric-names) that the unit be included as a suffix of the metric name. OpenMetrics goes a step further and -[requires this unit suffix](https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#unit). +[requires this unit suffix](https://github.com/prometheus/OpenMetrics/blob/v1.0.0/specification/OpenMetrics.md#unit). Currently, when exporting in Prometheus format from an OpenTelemetry SDK, the unit is added as a suffix to the metric name.