Add event_name as a top level field in the LogRecord.
#4652
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 task
aabmass
approved these changes
Jun 23, 2025
opentelemetry-api/src/opentelemetry/_logs/_internal/__init__.py
Outdated
Show resolved
Hide resolved
tammy-baylis-swi
approved these changes
Jun 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
event_namewas added to the log proto as a top level field: https://github.com/open-telemetry/opentelemetry-proto/releases/tag/v1.6.0We need to wait for #4645 to merge which upgrades the proto in this repo passed 1.5.
Also see open-telemetry/opentelemetry-specification#4260
This PR adds it to the API/SDK / LogRecord -> proto conversion function.
Fixes #4644
Type of change
How Has This Been Tested?
Unit tests
Does This PR Require a Contrib Repo Change?
Once this PR makes it into a release, I plan to update instrumentations using events to instead use the logs SDK and set this field in the log instead of using the deprecated events SDK.
Checklist: