Repository navigation
fix(chat): align tracing function and stub on top-level chat_id - #40
Merged
Merged
Conversation
The OWUI filter sent chat_id inside body.metadata while the outlet path relied on context keys Open WebUI does not populate, so chats fell back to a random id per hop and spans never matched a stable session. Send chat_id at the body top level (both inlet and outlet) and have the stub prefer it.
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
1 participant
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.
Follow-up to #37, verified live against Langfuse Cloud.
The OWUI filter sent chat_id inside body.metadata while its outlet path relied on context keys Open WebUI does not populate, so chats fell back to a random id per hop and inlet/outlet spans never landed on one stable session. Send chat_id at the body top level (both inlet and outlet) and have the stub prefer it over metadata.