Skip to main content
Info

If you are using LangChain, you can use LangChain’s native threads to track sessions! See https://docs.smith.langchain.com/old/monitoring/faq/threads

Evals in the Phoenix UI

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.

Example Notebooks#

Use CaseLanguageLinks
OpenAI tracing with SessionsPython
LlamaIndex tracing with SessionsPython
OpenAI tracing with SessionsTS/JS

Logging Conversations#

Below is an example of logging conversations:

First make sure you have the required dependencies installed

Note

Requires arize-phoenix-otel 0.16.0 or later for using_session and SpanAttributes to be importable directly from phoenix.otel. On older versions, import them from openinference.instrumentation and openinference.semconv.trace.

Below is an example of how to propagate session IDs to auto-instrumented spans.

Viewing Sessions#

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.

View all the sessions under a project

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.

Session details view

How to track sessions with LangChain#

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.