feat(ai-monitoring): Filter and sort whole conversations - #123899
Merged
Conversation
vgrozdanic
added this pull request to stack #123900
September 9, 2026 13:33
vgrozdanic
force-pushed
the
feat/conversation-query-aliases-only
branch
from
September 9, 2026 14:02
71a5ac9 to
ac5f650
Compare
vgrozdanic
removed this pull request from stack #123900
September 9, 2026 14:03
vgrozdanic
changed the base branch from
fix/search-query-aggregate-arguments
to
master
September 9, 2026 14:03
vgrozdanic
force-pushed
the
feat/conversation-query-aliases-only
branch
from
September 10, 2026 07:21
ac5f650 to
0ce5765
Compare
Pass aggregate conditions through to EAP and simplify conversation query compilation.
vgrozdanic
force-pushed
the
feat/conversation-query-aliases-only
branch
from
September 10, 2026 09:26
0ce5765 to
9359dbc
Compare
vgrozdanic
marked this pull request as ready for review
September 10, 2026 09:32
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.
AI conversation search now checks each condition against the whole conversation instead of requiring one span to match the entire query. For example, one agent span and one tool span can satisfy
agent:researcher AND tool:search.Each span condition becomes “this conversation has at least one matching span”:
Boolean logic and parentheses stay unchanged. Table aliases such as
totalCostexpand to EAP aggregates, while explicit aggregates pass through as written. Negated conditions require zero matching spans.Closes TET-2904: Support group filtering for conversations