Extract request's trace context in GenerateStream()
#64
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
This PR applies the logic of extracting request's trace context in
GenerateStream()
as done inGenerate()
This is a followup on #20.
How Has This Been Tested?
I set up a local environment where I ran
vllm-tgis-adapter
andfmaas-router
.Additionally, I ran
jaeger
and configured bothvllm-tgis-adapter
andfmaas-router
to export traces tojaeger
.Then, I sent a
GenerateStream
request usinggrpcurl
tofmaas-router
and verified that there is a single trace in Jaeger containg spans from bothvllm-tgis-adapter
andfmaas-router
.Merge criteria: