ref(seer): Remove Langfuse URL plumbing from Seer Explorer - #121186
Merged
Conversation
Langfuse tracing is being killed in favor of Sentry's own AI tracing, so the Langfuse deep links no longer point anywhere useful. Deletes the getLangfuseUrl util and every consumer: the langfuse_url analytics property on seer.explorer.feedback_submitted, the langfuse_url feedback tag, and the employee-only /langfuse slash command (along with its now unused onLangfuse handler prop). The /conversations slash command already covers this use case with the Sentry AI trace view.
github-actions
Bot
added
the
Scope: Frontend
aliu39
marked this pull request as ready for review
August 4, 2026 17:25
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.
Langfuse tracing is being killed in favor of Sentry's own AI tracing, so the Langfuse deep links scattered through Seer Explorer no longer point anywhere useful. This removes the
getLangfuseUrlutil and every consumer of it.What's removed
getLangfuseUrl()instatic/app/views/seerExplorer/utils.tsx(hardcodedlangfuse.getsentry.netsession URL)langfuse_urlfrom theseer.explorer.feedback_submittedanalytics event definition and its call sitelangfuse_urltag attached to Seer Explorer user-feedback submissions/langfuseslash command, plus the now-unusedonLangfusehandler prop onSlashCommandHandlersand thehandleOpenLangfusecallbackWhy it's safe
The
/conversationsslash command and theconversations_urlanalytics property/feedback tag already cover the same debugging need via the Sentry AI trace view, so nothing is left without an equivalent.langfuse_urlwas write-only telemetry — dropping the property just stops sending a dead link.Frontend-only; no backend changes.