feat: emit runtime events from third-party OTel spans - #127
Merged
Merged
Conversation
Signed-off-by: Pavan Sudheendra <pavan0591@gmail.com>
|
Great addition of runtime events from third-party OTel spans. Useful feature, ready to merge! |
1 similar comment
|
Great addition of runtime events from third-party OTel spans. Useful feature, ready to merge! |
topology.node.completed now includes agent.output, topology listeners expose agent_output, third-party GenAI spans map gen_ai.output.messages, and materialized nodes store output. Schema, docs, and regression coverage were updated. Signed-off-by: Pavan Sudheendra <pavan0591@gmail.com>
Signed-off-by: Pavan Sudheendra <pavan0591@gmail.com>
2 tasks
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
2 participants
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
Add a span processor that maps GenAI semantic-convention spans to
Observe lifecycle events and exports them asynchronously through a
private OTel Logs pipeline.
Include per-session ordering, trace correlation, collector forwarding,
focused tests, and a runnable third-party SDK example.
Type of Change
Checklist