You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the current implementation of Arize Phoenix, it seems that the functionality you're requesting is partially available. The Session class, which maintains a 1-1 shared state with the Phoenix App, already supports specifying a remote host and port. This means that you can run the Phoenix App on a remote server and interact with it from a notebook.
However, the current implementation assumes that the datasets (including traces) are available locally when the Session is initialized. If your datasets are also stored on the remote server, you would need to load them into your local environment before initializing the Session.
Here's a simplified example of how you might do this:
# Load datasets from remote serverprimary_dataset=load_dataset_from_remote('primary_dataset_path')
trace_dataset=load_trace_dataset_from_remote('trace_dataset_path')
# Initialize session with remote host and portsession=Session(
primary_dataset=primary_dataset,
trace_dataset=trace_dataset,
host='remote_host',
port='remote_port'
)
In this example, load_dataset_from_remote and load_trace_dataset_from_remote are hypothetical functions that you would need to implement. These functions should download the datasets from the remote server and return them in a format that can be passed to the Session constructor.
As for sending evaluations, the current implementation does not seem to support this directly. However, you could potentially implement this functionality by extending the Session class and adding a method for sending evaluations to the remote server.
Please note that these are just suggestions and might require further adjustments based on the specifics of your remote server and how you have set up your Arize Phoenix environment.
As a user I still want to be able to interact with phoenix in a notebook even if it's running in a remote server. As a user I want to:
The UX for interacting with a remote session should ideally be no different than a local one
The text was updated successfully, but these errors were encountered: