-
Notifications
You must be signed in to change notification settings - Fork 427
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR]: Filter in span search for speed improvement #1624
Comments
Hey @gustavhartz , thank you for the idea! We will check it and try to implement soon :) Shouldn't take that long |
Great! Looking forward, would be very helpful |
@gustavhartz We're thinking of adding a "search all fields" options rather than adding specific filters - Would be much easier to use I think. Are you mostly interested in searching by name / input / output / metadata / type fields or also the others (feedback scores, tokens, etc) |
Hey @gustavhartz , This feature was merged into the main with the next #1646 and has already been deployed to production. I am closing this ticket as done. Please reopen it in case you have any issues. |
Proposal summary
Implement a search field that can be leveraged to faster search trace spans. e.g. in the case below
Motivation
The text was updated successfully, but these errors were encountered: