From c6f79a908f681f5b618c94bee3a731faeea1e10d Mon Sep 17 00:00:00 2001 From: David Ashpole Date: Wed, 12 Jun 2024 09:47:00 -0400 Subject: [PATCH] Update content/en/blog/2024/prometheus-compatibility-survey/index.md Co-authored-by: Fabrizio Ferri-Benedetti --- 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 5bc5eac38787..a11efe0194eb 100644 --- a/content/en/blog/2024/prometheus-compatibility-survey/index.md +++ b/content/en/blog/2024/prometheus-compatibility-survey/index.md @@ -27,7 +27,7 @@ Prometheus Receiver and Prometheus exporters. One of the most challenging areas to reconcile is that OpenTelemetry metric names are changed when exporting to Prometheus. Today, the OpenTelemetry `http.server.request.duration` metric, with unit `s`, is translated to -`http_server_request_duration_seconds` in Prometheus. Some users are familar +`http_server_request_duration_seconds` in Prometheus. Some users are familiar with the Prometheus naming conventions, and appreciate the consistency this translation provides with existing metrics in the Prometheus ecosystem. Other users are confused when querying for the original OpenTelemetry name does not