feat(seer): Add structured LLM context for traces explorer page#114347
Merged
Mihir-Mavalankar merged 1 commit intomasterfrom Apr 29, 2026
Merged
feat(seer): Add structured LLM context for traces explorer page#114347Mihir-Mavalankar merged 1 commit intomasterfrom
Mihir-Mavalankar merged 1 commit intomasterfrom
Conversation
Contributor
Mihir-Mavalankar
commented
Apr 29, 2026
Mihir-Mavalankar
commented
- Give the Seer Explorer agent structured page context on the /explore/traces/ route instead of falling back to the ASCII DOM snapshot. The context captures the user's current search query, active tab, visualize metrics, group-by fields, and sort order, plus tool-call hints so the agent knows how to drill deeper.
Give the Seer Explorer agent structured page context on the /explore/traces/ route instead of falling back to the ASCII DOM snapshot. The context captures the user's current search query, active tab, visualize metrics, group-by fields, and sort order, plus tool-call hints so the agent knows how to drill deeper. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
github-actions
Bot
added
the
Scope: Frontend
JonasBa
approved these changes
Apr 29, 2026
Mihir-Mavalankar
added a commit
that referenced
this pull request
May 1, 2026
+ Replace the ASCII DOM snapshot with structured semantic context on the /issues/ page for the Seer Explorer agent. Registers an 'issue-list' node type that pushes query filters, sort order, issue count, page filters, and a compact pipe-delimited CSV of the 25 visible issues (shortId, title, type, level, priority, events, users, firstSeen) into the LLM context tree. + Current p50 for this page is [5700 tokens](https://redash.getsentry.net/queries/10910). I am estimating this will bring it down to ~1200. + Gated behind the context-engine-structured-page-context flag via NEW_STRUCTURED_CONTEXT_ROUTES. ONly open to 4 internal users. + Similar work on other pages: + Trace details page -#114093 + Traces explore page - #114347 + Dashboard page - #111973 + Shipped post: https://vanguard.getsentry.net/p/cmodhfvfr00033pvr5owrfnke Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
3 tasks
cleptric
pushed a commit
that referenced
this pull request
May 5, 2026
) + Give the Seer Explorer agent structured page context on the /explore/traces/ route instead of falling back to the ASCII DOM snapshot. The context captures the user's current search query, active tab, visualize metrics, group-by fields, and sort order, plus tool-call hints so the agent knows how to drill deeper. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
cleptric
pushed a commit
that referenced
this pull request
May 5, 2026
+ Replace the ASCII DOM snapshot with structured semantic context on the /issues/ page for the Seer Explorer agent. Registers an 'issue-list' node type that pushes query filters, sort order, issue count, page filters, and a compact pipe-delimited CSV of the 25 visible issues (shortId, title, type, level, priority, events, users, firstSeen) into the LLM context tree. + Current p50 for this page is [5700 tokens](https://redash.getsentry.net/queries/10910). I am estimating this will bring it down to ~1200. + Gated behind the context-engine-structured-page-context flag via NEW_STRUCTURED_CONTEXT_ROUTES. ONly open to 4 internal users. + Similar work on other pages: + Trace details page -#114093 + Traces explore page - #114347 + Dashboard page - #111973 + Shipped post: https://vanguard.getsentry.net/p/cmodhfvfr00033pvr5owrfnke Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
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.