Log record mutations are visible in next registered processors (open-…

…telemetry#4067) ### Current description Closes open-telemetry#4065
carlosalberto · Sep 4, 2024 · 4e40e67 · 4e40e67
1 parent 1d5afcf
commit 4e40e67
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 0 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -21,6 +21,9 @@ release.
 
 ### Logs
 
+- Clarify that log record mutations are visible in next registered processors.
+  ([#4067](https://github.com/open-telemetry/opentelemetry-specification/pull/4067))
+
 ### Events
 
 ### Baggage

diff --git a/specification/logs/sdk.md b/specification/logs/sdk.md
@@ -324,6 +324,9 @@ therefore it SHOULD NOT block or throw exceptions.
 
 **Returns:** `Void`
 
+For a `LogRecordProcessor` registered directly on SDK `LoggerProvider`,
+the `logRecord` mutations MUST be visible in next registered processors.
+
 A `LogRecordProcessor` may freely modify `logRecord` for the duration of
 the `OnEmit` call. If `logRecord` is needed after `OnEmit` returns (i.e. for
 asynchronous processing) only reads are permitted.