Repository navigation
feat(cmdk): Tag Seer chats started from the command palette - #130985
Open
sentry-junior[bot] wants to merge 1 commit into
Open
sentry-junior[bot] wants to merge 1 commit into
sentry-junior[bot] wants to merge 1 commit into
Conversation
Pass where a forwarded query came from (Tab or the no-results Ask Seer item) through to the explorer-chat POST that starts the run, and add it to the session_created analytics event as entry_point. Continued runs never send it. Co-Authored-By: Nate Moore <7118177+natemoo-re@users.noreply.github.com> Co-Authored-By: Matt Duncan <matt.duncan@sentry.io>
github-actions
Bot
added
the
Scope: Frontend
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
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.
The command palette hands its query to Seer Explorer in two ways: Tab (even when there are results) and the no-results "Ask Seer: …" item. Either way the query is sent automatically as the first message. A lot of these first messages look like palette lookups (
dsn,client keys, issue short IDs), and right now we can't separate them from chats started in the panel.This PR records which handoff started the chat:
CommandPalettepassesinitialQueryReferrer: 'command_palette.tab' | 'command_palette.no_results'toopenSeerExplorer.initialQuerythrough the drawer, the sidebar context/panel and the PiP sidebar content intoSeerExplorerContent's auto-submit.useSeerExplorer.sendMessagetakes it as an optional trailing argument. It sendsreferreron the POST only when the message starts a new run, and addsentry_pointtoseer.explorer.session_created.The backend side (accepting
referrerand storing it onSeerRun.referrer) is a separate PR. DRF ignores unknown fields, so either PR can land first. Until the backend is deployed, the analyticsentry_pointstill works on its own.Existing
sendMessageassertions were updated for the new trailing argument. New tests cover both palette handoffs, the sidebar pass-through, and "referrer on new runs only".via @natemoo-re.
--
View Session [Sentry]