feat(profiling): Use spans data source for profiles search bar in EAP mode#111772
Merged
Conversation
… mode When useTransactionSummaryEAP is enabled, use TraceItemSearchQueryBuilder with the spans data source instead of TransactionSearchQueryBuilder. Also pass dataSource: 'spans' to useAggregateFlamegraphQuery and use is_transaction:true instead of event.type:transaction in the query filter. Follows the same pattern established in transactionEvents/content.tsx. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
github-actions
Bot
added
the
Scope: Frontend
nsdeschenes
approved these changes
Mar 30, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When useTransactionSummaryEAP is enabled, use TraceItemSearchQueryBuilder with the spans data source instead of TransactionSearchQueryBuilder. Also pass dataSource: 'spans' to useAggregateFlamegraphQuery and use is_transaction:true instead of event.type:transaction in the query filter.
Follows the same pattern established in transactionEvents/content.tsx.