From 0f5ec2aa4091c80a53e456f0bc7f738ff09754c0 Mon Sep 17 00:00:00 2001 From: Uladzislau Kiva Date: Mon, 15 Jun 2020 18:35:15 +0300 Subject: [PATCH] docs: change SumObserver to UpDownSumObserver because before we were mention UpDownSumObserver (#642) --- specification/metrics/api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/metrics/api.md b/specification/metrics/api.md index 3c1442104e6..a1068786cab 100644 --- a/specification/metrics/api.md +++ b/specification/metrics/api.md @@ -641,7 +641,7 @@ opposed to `UpDownSumObserver`? Consider how to report the size of a queue asynchronously. Both `ValueObserver` and `UpDownSumObserver` logically apply in this case. Asynchronous instruments capture only one measurement per interval, so -in this example the `SumObserver` reports a current sum, while the +in this example the `UpDownSumObserver` reports a current sum, while the `ValueObserver` reports a current sum (equal to the max and the min) and a count equal to 1. When there is no aggregation, these results are equivalent.