-
Notifications
You must be signed in to change notification settings - Fork 543
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dashboard: Traces & Log messages - viewer for long fields #4412
Comments
This feels very important. Makes the dashboard a bit unusable with large text values. |
TODO: Figure out an owner here. |
@kvenkatrajan for assignment. |
@samsp-msft we already have a button there for copying the grid value. We could replace with a button that opens a little tooltip where you can choose your action? Or we could put both buttons inline. |
As per discussion with @leslierichardson95 and @samsp-msft, we would like to have a button to open a menu, where you will be able to choose whether to open this popup or copy the cell text. |
Sweet! |
There is an initiative to use OTel to provide telemetry for LLM applications - recording the prompt and response text. These are typically long and can be plain text or json. When looking at these in the Aspire dashboard, in the trace and logs view, the details pane has a one line display with a "..." and button to copy to the dashboard.
Visual Studio debugger has the same problem when its showing variables in the watch window. It has an option to pop out the value in a modal dialog, where text can be more easily examined. We should have something similar for the dashboard.
When the text is opened in the viewer, we should have a quick mechanism to sniff to see if it looks to be json, and then provide an option to format the content as json - as it typically will not have any formatting. The VS one has the ability to do base64, url encoding/decoding. Those are probably not needed here, but JSON and possibly XML formatting would be very useful.
If it fails to parse that would also be really useful to know, so spitting out the error in those cases would be good.
The text was updated successfully, but these errors were encountered: