Skip to content
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

[Big Trace] Move search in Trace to Backend #3603

Closed
Tracked by #3599
xoscar opened this issue Feb 6, 2024 · 0 comments · Fixed by #3611
Closed
Tracked by #3599

[Big Trace] Move search in Trace to Backend #3603

xoscar opened this issue Feb 6, 2024 · 0 comments · Fixed by #3611
Assignees

Comments

@xoscar
Copy link
Collaborator

xoscar commented Feb 6, 2024

Currently, as part of the trace tab Tracetest supports searching for spans by two types of criteria:

  1. Using the selector approach (similar to the one we use for the test spec creation) from the BE
  2. Full-text search, where we look at the full list of attributes of a span, including id and name happening at the FE

With large-span data, the second option causes a big delay and breaks the UI and it is a costly operation executed on the browser side and blocks some other options in the UI.

The idea is to have a centralized service where users can search for spans in a test run trace using both the selector query language and full text.

This will also be useful for the analyzer section, where for large traces we are going to enable users to look for specific span results.

@xoscar xoscar changed the title Search Move search in Trace to Backend Feb 6, 2024
@xoscar xoscar assigned schoren and xoscar and unassigned xoscar Feb 6, 2024
@jorgeepc jorgeepc changed the title Move search in Trace to Backend [Big Trace] Move search in Trace to Backend Feb 6, 2024
@schoren schoren linked a pull request Feb 8, 2024 that will close this issue
@xoscar xoscar self-assigned this Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants