Tracing UI beta requirements

Overview

Goal of this issue is to define functional UI requirements for Tracing beta release, based on Mikhail interview to migrate from Jaeger UI.

See epic for context.

Next steps:

• Interview Mikhail / KAS to gather needs - notes - TLDR: relatively simple requirements. Doesn't use any advanced features like trace comparison
• Discuss feasibility with Daniele - notes - TLDR: can address most requirements with existing UI components. but may need more back-end API work than expected.
• Create issues
• Prioritize issues

Requirements

Pre-fill values

• P1 - Must-have
  •   Add prepopulated Period filter to tracing searc... (#2379 - closed) • Daniele Rossetti • 16.5
  • https://gitlab.com/gitlab-org/opstrace/opstrace/-/issues/2369+s (in review)

Search/Filter

• P1 - Must-have
  •   https://gitlab.com/gitlab-org/opstrace/opstrace/-/issues/2381+s
• P2 - should-have
  • Search traces by custom time range (#2380 - closed) • Daniele Rossetti • 16.7- --> Non-blocking for Beta
  • https://gitlab.com/gitlab-org/opstrace/opstrace/-/issues/2382+s - Need BE
  • https://gitlab.com/gitlab-org/opstrace/opstrace/-/issues/2383+s - Need BE + blocked by #2381

Results list

• P1 - must-have
  •   frontend: Add Infinite Scrolling to tracing list (#2272 - closed) • Daniele Rossetti • 16.5
  • https://gitlab.com/gitlab-org/opstrace/opstrace/-/issues/2384+s - (in review)
  • https://gitlab.com/gitlab-org/opstrace/opstrace/-/issues/2385+s - Need BE

Trace detail page

• P1 - must-have
  •   Tracing duration is not accurate (#2395 - closed) • Daniele Rossetti • 16.5
  •   https://gitlab.com/gitlab-org/opstrace/opstrace/-/issues/2354+s
  • https://gitlab.com/gitlab-org/opstrace/opstrace/-/issues/2388+s - Design discussion WIP