In my use case I have to deal with many large-ish payloads.
We find the web UI super helpful for debugging and other trace analysis.
In particular, in order to improve the system (which uses generative AI) we need to be able to view our payloads in some detail.
To prevent the history from getting too large (we’ve had some overflows), we will probably have to handle this in an artifact store, meaning we will no longer be able to view payload data directly in the UI.
Currently we can view data by copying the blob id and pasting it into a url or search box in another window, but that adds cognitive load and takes time when navigating many traces.
Clickable links would be better.
One option is to maintain a sequence of payload view links in the description markdown, but that doesn’t explicitly link to activities so it’s less useful for large traces.
Memos would be better, but I believe they are just rendered as plain text? And they also don’t link explicitly to activities.
I’d like to be able to attach more general formatting to activity data (whether it’s the ability to render markdown, embed a more complex data view, or something else).
If there are any features that cover this sort of consideration please let me know!
Otherwise, here are some random ideas for how this could be accomplished:
- workflow/activity can attach activity mime-typed metadata to completed activity executions, which is then rendered according to type in the UI (could cover links and also potentially things like simple graphs)
- attach a link that is displayed as an iframe – would allow general customization
- attach a markdown template to the activity (either from the activity definition or from the activity execution call) that can pull from the payload