Closed davehorton closed 1 year ago
Additionally, that call shows a usability problem when we have a call with a lot of traces: the detail panel at the bottom is pushed way down, so that if you want to see the details of a span that you click on you then have to scroll the window a lot to see those details. It is not good when the summary line and the associated detail can not be seen together.
So I would like to change how we show the detail. Instead of showing it in a panel section below the tracing lines, please show it in a modal dialog that pops up when you mouseover a higher-level tracing line. For instance, when you mouseover "verb:hook" you would see the details for that hook pup in a dialog to the right of the title (verb:hook) and then disappear when your mouse leaves that row
Also, we need to have an env var which, if set, makes it so we do not show the tracing panel at all in recent calls (i.e., the view should look exactly like those calls for which we do not have a trace_id)
Another issue is that long lines in the detail view are getting truncated. We need the text to wrap into multiple lines in this case so we can see it all. Example below with stt.result:
Closed as PR merged
In the tts span the 'cached' property, which should show true or false, is blank
Please see call placed at 05.08.2023 1:19 PM for example