From 9ffa45ab158ea4771a1616590ca9db2f5f0e8529 Mon Sep 17 00:00:00 2001 From: Tyler Yahn Date: Thu, 4 Jan 2024 09:10:23 -0800 Subject: [PATCH] Specify limiting and filtering interaction Resolve #3798 --- specification/metrics/sdk.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/specification/metrics/sdk.md b/specification/metrics/sdk.md index 47fc44fda3b..5b061bae7af 100644 --- a/specification/metrics/sdk.md +++ b/specification/metrics/sdk.md @@ -40,6 +40,7 @@ linkTitle: SDK + [Overflow attribute](#overflow-attribute) + [Synchronous instrument cardinality limits](#synchronous-instrument-cardinality-limits) + [Asynchronous instrument cardinality limits](#asynchronous-instrument-cardinality-limits) + + [Interaction with filtering](#interaction-with-filtering) - [Meter](#meter) * [Duplicate instrument registration](#duplicate-instrument-registration) + [Name conflict](#name-conflict) @@ -776,6 +777,13 @@ Aggregators of asynchronous instruments SHOULD prefer the first-observed attributes in the callback when limiting cardinality, regardless of temporality. +#### Interaction with filtering + +It is left unspecified if attribute filtering from a user provided view needs +to be applied before or after applying the cardinality limit. While this can +lead to inconsistent telemetry across implementations, this will only happen in +an error scenario where a cardinality limit is used. + ## Meter Distinct meters MUST be treated as separate namespaces for the purposes of detecting