You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, as part of the trace tab Tracetest supports searching for spans by two types of criteria:
Using the selector approach (similar to the one we use for the test spec creation) from the BE
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.
The text was updated successfully, but these errors were encountered:
Currently, as part of the trace tab Tracetest supports searching for spans by two types of criteria:
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.
The text was updated successfully, but these errors were encountered: