Separate RPC events from spans#3226
Merged
lmolkova merged 3 commits intoopen-telemetry:mainfrom Jan 10, 2026
Merged
Conversation
lmolkova
commented
Dec 17, 2025
lmolkova
moved this from Untriaged
to Awaiting codeowners approval
in Semantic Conventions Triage
Contributor
There was a problem hiding this comment.
Pull request overview
This PR separates RPC events from spans following OTEP-265 and OTEP-4430, which deprecate span events in favor of log-based events. The changes move event definitions to a standalone file and documentation, enabling RPC spans to be stabilized independently from events, which will remain in development status.
Key changes:
- Creates a new
model/rpc/events.yamlfile containing therpc.messageevent definition - Removes event references from RPC span definitions in
model/rpc/spans.yaml - Separates event documentation into a new
docs/rpc/rpc-events.mdfile
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
model/rpc/spans.yaml |
Removed events: [rpc.message] from client and server span definitions, and deleted the embedded event definition |
model/rpc/events.yaml |
New file defining the rpc.message event with attributes for message type, ID, compressed size, and uncompressed size |
docs/rpc/rpc-spans.md |
Removed the Events section and Message event documentation; removed duplicate technology-specific conventions section |
docs/rpc/rpc-events.md |
New file documenting RPC events with the Message event specification |
docs/rpc/README.md |
Added reference to the new RPC Events documentation |
matt-hensley
approved these changes
Dec 19, 2025
lmolkova
commented
Dec 20, 2025
lmolkova
commented
Dec 20, 2025
lmolkova
commented
Dec 20, 2025
4 tasks
|
This PR has been labeled as stale due to lack of activity. It will be automatically closed if there is no further activity over the next 7 days. |
trask
approved these changes
Jan 7, 2026
github-project-automation
bot
moved this from In Progress
to Done
in RPC Semantic Conventions Stability
Cirilla-zmh
pushed a commit
to Cirilla-zmh/semantic-conventions
that referenced
this pull request
Feb 3, 2026
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
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.
Following OTEP-265 and 4430 span events are deprecated.
Events in semantic conventions are intended for log-based events and there is effectively no means to record span events.
This PR separates events from spans in model and markdown. When stabilizing RPC we also plan to stabilize spans, but not events/