From 601651a5fd768b67f89626522727584cb152aca3 Mon Sep 17 00:00:00 2001 From: Ivana Kellyer Date: Thu, 18 Dec 2025 16:22:10 +0100 Subject: [PATCH] fix(develop): Clearer wording for attrs on current scope --- develop-docs/sdk/telemetry/scopes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/develop-docs/sdk/telemetry/scopes.mdx b/develop-docs/sdk/telemetry/scopes.mdx index 3045b950e6287..436d735c6d584 100644 --- a/develop-docs/sdk/telemetry/scopes.mdx +++ b/develop-docs/sdk/telemetry/scopes.mdx @@ -98,7 +98,7 @@ The method SHOULD accept a dictionary/map/object where: - Attributes set on the global scope MUST be applied to all logs and metrics - Attributes set on the isolation scope MUST be applied to all logs and metrics in that execution context -- Attributes set on the current scope MUST be applied only to the current log and current metric +- Attributes set on the current scope MUST be applied only to the logs and metrics that are captured while that current scope is active - When the same attribute key exists in multiple scopes, the more specific scope's value takes precedence (current > isolation > global) - When the same attribute key exists on the current log or metric, it MUST take precedence over an attribute with the same key set on any scope (log/metric > current > isolation > global) - The SDK SHOULD keep the attribute format consistent with the user-set format until user-provided processing callbacks like `before_send_log` have been called. This ensures compatibility with already existing callbacks and avoids unexpected changes to the attribute format.