Last updated
Last updated
Sessions UI is available in Phoenix 7.0 and requires a db migration if you're coming from an older version of Phoenix.
If you are using LangChain, you can use LangChain's native threads to track sessions! See
A Session
is a sequence of traces representing a single session (e.g. a session or a thread). Each response is represented as its own trace, but these traces are linked together by being part of the same session.
To associate traces together, you need to pass in a special metadata key where the value is the unique identifier for that thread.
Below is an example of logging conversations:
First make sure you have the required dependancies installed
Below is an example of how to use openinference.instrumentation
to the traces created.
You can view the sessions for a given project by clicking on the "Sessions" tab in the project. You will see a list of all the recent sessions as well as some analytics. You can search the content of the messages to narrow down the list.
You can then click into a given session. This will open the history of a particular session. If the sessions contain input / output, you will see a chatbot-like UI where you can see the a history of inputs and outputs.
For LangChain, in order to log runs as part of the same thread you need to pass a special metadata key to the run. The key value is the unique identifier for that conversation. The key name should be one of:
session_id
thread_id
conversation_id
.
How to track sessions across multiple traces
OpenAI tracing with Sessions
Python
LlamaIndex tracing with Sessions
Python
OpenAI tracing with Sessions
TS/JS