[DoNotMerge] ReadableLogRecord is able to access the passed context #3908
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #3907
Changes
Clarify that
ReadableLogRecord
is able to access all information added via "Emit a log record".This is needed so that the SDK is able to get access to the passed
Context
(https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/bridge-api.md#emit-a-logrecord) which can contain e.g. some baggage that may want to be used e.g. by custom processors.I think that the original intention of the spec authors was "Emit a Record" as "LogRecord" data model already defined fields that are later defined in
ReadableLogRecord
(e.g. Instrumentation Scope, Resource).