From 187a5fd18254d57ccce71f1fcc42b037b480df92 Mon Sep 17 00:00:00 2001 From: Ruslan Kovalov Date: Tue, 17 Jan 2023 16:23:25 +0100 Subject: [PATCH] [chore] Fix wrong metric type in OTel to Prom compatibility section. --- specification/compatibility/prometheus_and_openmetrics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/compatibility/prometheus_and_openmetrics.md b/specification/compatibility/prometheus_and_openmetrics.md index e48ba4fc64c..6e25fd51479 100644 --- a/specification/compatibility/prometheus_and_openmetrics.md +++ b/specification/compatibility/prometheus_and_openmetrics.md @@ -261,7 +261,7 @@ An [OpenTelemetry Gauge](../metrics/data-model.md#gauge) MUST be converted to a - If the aggregation temporality is cumulative and the sum is monotonic, it MUST be converted to a Prometheus Counter. - If the aggregation temporality is cumulative and the sum is non-monotonic, it MUST be converted to a Prometheus Gauge. -- If the aggregation temporality is delta and the sum is monotonic, it SHOULD be converted to a cumulative temporality and become a Prometheus Sum. The following behaviors are expected: +- If the aggregation temporality is delta and the sum is monotonic, it SHOULD be converted to a cumulative temporality and become a Prometheus Counter. The following behaviors are expected: - The new data point type must be the same as the accumulated data point type. - The new data point's start time must match the time of the accumulated data point. If not, see [detecting alignment issues](../metrics/data-model.md#sums-detecting-alignment-issues). - Otherwise, it MUST be dropped.