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
While preparing a demo for .NET9's experimental connection tracing feature, I discovered that after clicking View on the span link, the UI is showing the wrong span (keeps visualizing the request span):
I would like to see the linked connection_setup span expanded with it's subspans. To get there quickly, I tried to paste the spanID into the filter input box, but it filters by name by default, so eventually the quickest solution was to find the correct connection_setup span manually by scrolling down and using the browser's search function:
This feels like a bug, or if it works like this by design, the UX is clearly sub-optimal.
The text was updated successfully, but these errors were encountered:
While preparing a demo for .NET9's experimental connection tracing feature, I discovered that after clicking
View
on the span link, the UI is showing the wrong span (keeps visualizing the request span):I would like to see the linked
connection_setup
span expanded with it's subspans. To get there quickly, I tried to paste the spanID into the filter input box, but it filters by name by default, so eventually the quickest solution was to find the correctconnection_setup
span manually by scrolling down and using the browser's search function:This feels like a bug, or if it works like this by design, the UX is clearly sub-optimal.
The text was updated successfully, but these errors were encountered: