feat(dashboard): Show event model configuration and call usage - #1946
Merged
Merged
Conversation
Co-Authored-By: Daniel Griesser <dgriesser@sentry.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
5 screenshot changes — 5 changed · 0 added · 0 removed Review screenshots in Frameshift
|
HazAT
marked this pull request as ready for review
September 25, 2026 20:08
Co-Authored-By: Daniel Griesser <dgriesser@sentry.io>
HazAT
approved these changes
Sep 28, 2026
This branch was successfully deployed
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.
Show the recorded model ID, model profile, and reasoning level in event rows and at the top of event details. Handoff entries identify the target configuration. Call entries show token counters, cache reads and writes, reasoning tokens, and estimated USD costs. Router cost stays separate.
The reporting API now retains allowlisted model-call metadata, including text-only calls whose usage was previously absent from the event log. Tool starts and results do not repeat that usage. Bounded lookups preserve model context across event pages, and turn boundaries clear it. Missing settings remain unknown rather than using current host configuration.
The transcript still omits metadata-only calls. Private payload redaction and the raw JSON disclosure remain intact.
via daniel.
--
View Junior Session [Sentry]