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
It would be very nice to link automatically traceId's to the corresponding trace view if it's listed inside a table (from a dashboard). That would make the UX much better.
Describe alternatives you've considered
I copy the traceId to the clipboard
open some trace (any fits)
select the text in the URL from browser from traceId to end
paste the copied traceId from clipboard
press enter
Obviously the workaround is annoying....
Additional context
Add any other context or screenshots about the feature request here.
Thank you for your feature request – we love each and every one!
The text was updated successfully, but these errors were encountered:
Sounds very good, I also can imagine something like a special name for the column in case we want it to get linked (or keep it genuine like traceID & the system would assume that then matches an existing id). In general I strongly believe the added value of such a system comes from a good interlinking between the different sparse items. This is a bit missing in the "detached" views like dashboards etc. I think this might be only the beginning of more things to come up. I mean by that, it should also get some care in implementing it in a well reusable and extensible way. But I'm sure you'll do that anyways :-)
Is your feature request related to a problem?
Improve the UX regarding traceId linkage.
Describe the solution you'd like
It would be very nice to link automatically traceId's to the corresponding trace view if it's listed inside a table (from a dashboard). That would make the UX much better.
Describe alternatives you've considered
Obviously the workaround is annoying....
Additional context
Add any other context or screenshots about the feature request here.
Thank you for your feature request – we love each and every one!
The text was updated successfully, but these errors were encountered: