feat: surface request parameters in trace detail metadata#442
feat: surface request parameters in trace detail metadata#442
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@claude rebase to main |
|
Claude finished @heiwen's task in 15s —— View job Rebase RequestI'm unable to perform git rebase operations due to my current capabilities — I can only create and push commits, not rebase, merge, or perform other complex git operations. You can rebase locally with: git fetch origin main
git rebase origin/main
git push --force-with-lease origin claude-issue-423-20260423-0133You can find more information and potential workarounds in the FAQ. |
Add a "Request Parameters" section to the Metadata tab in the trace detail view, displaying gen_ai.request.* span attributes (stream, temperature, max_tokens, top_p, frequency_penalty, presence_penalty, stop_sequences, seed, service_tier). Backend: dynamically discover and fetch request parameter columns from GreptimeDB (unaliased so they flow into spanAttributes). Frontend: extract and render matching keys under a new section. Mocks: add request parameter attributes to several mock traces. Closes #423 Co-authored-by: Heinrich Wendel <heiwen@users.noreply.github.com>
dae8d27 to
c48695d
Compare
Add a "Request Parameters" section to the Metadata tab in the trace detail view, surfacing gen_ai.request.* span attributes (stream, temperature, max_tokens, top_p, frequency_penalty, presence_penalty, stop_sequences, seed, service_tier).
Closes #423
Generated with Claude Code