Hey what do you recommand for tracing chat conversations? Should one chain hold the full conversation. Or should one chain hold just one interaction?
Good question Remi, we鈥檙e actually going to support sessions and conversations in the coming months. We are thinking you correlate traces with a session id. This lets you view conversations as individual interactions as well as a top level thread. Does this align with what you were thinking?
But what do you recommand for now? One chain per interaction?
I think so yeah. You can add a conversation ID or session ID to the metadata attributes. You should then be able to recreate the conversation via filters
Another question I'm wondering: I want to use chainlit to implement a chat frontend, is there a way I can save the dataframe after each message?
(I also want to hook up the feedback functions to the eval function of phoenix)
We have persistence coming pretty soon but no there鈥檚 no easy way to hook in to the completion of a trace. You definitely can save on a periodic basis.
Yeah the human feedback comes up for us for sure. We will have a way of annotating traces and conversations with human feedback but right now it鈥檚 a bit difficult
So there's no way to know when I'm sending the trace what the span id is, is that correct?
It鈥檚 not entirely impossible I think - I think it would probably be easier though if you controlled your own ID system so you could join back the feedback on an ID you control (add the id to the metadata then join back the feedback and log as an eval). It I was on a time crunch I鈥檇 try that. Sorry for now having an elegant solution for ya
Assuming I'm running on the same node, can I access px.Client() from the code outside of the notebook?
Or does the client need to come from the notebook that launched phoenix?
