Clarify guidance regarding excessive logging (open-telemetry#3151)

CHANGELOG.md

@@ -11,13 +11,21 @@ release.
 
 ### Traces
 
+- Clarify guidance regarding excessive logging when attributes are dropped
+  or truncated.
+  ([#3151](https://github.com/open-telemetry/opentelemetry-specification/pull/3151))
+
 ### Metrics
 
 ### Logs
 
 - Define BatchLogRecordProcessor default configuration values.
   ([#3002](https://github.com/open-telemetry/opentelemetry-specification/pull/3002))
 
+- Clarify guidance regarding excessive logging when attributes are dropped
+  or truncated.
+  ([#3151](https://github.com/open-telemetry/opentelemetry-specification/pull/3151))
+
 ### Resource
 
 ### Semantic Conventions

specification/logs/sdk.md

@@ -153,8 +153,8 @@ public interface LogRecordLimits {
 
 There SHOULD be a message printed in the SDK's log to indicate to the user
 that an attribute was discarded due to such a limit.
-To prevent excessive logging, the message should not be printed once per
-`LogRecord` or per discarded attribute.
+To prevent excessive logging, the message MUST be printed at most once per
+`LogRecord` (i.e., not per discarded attribute).
 
 ## LogRecordProcessor
 

specification/trace/sdk.md

@@ -412,9 +412,10 @@ public final class SpanLimits {
 * `AttributePerEventCountLimit` (Default=128) - Maximum allowed attribute per span event count;
 * `AttributePerLinkCountLimit` (Default=128) - Maximum allowed attribute per span link count;
 
-There SHOULD be a log emitted to indicate to the user that an attribute, event,
-or link was discarded due to such a limit. To prevent excessive logging, the log
-should not be emitted once per span, or per discarded attribute, event, or links.
+There SHOULD be a message printed in the SDK's log to indicate to the user
+that an attribute was discarded due to such a limit.
+To prevent excessive logging, the message MUST be printed at most once per
+span (i.e., not per discarded attribute, event, or link).
 
 ## Id Generators