Configuration¶
The UI and API stay on loopback. Writes use the per-instance token. Reads are available to local users and to anyone who can open the tunnel.
Where things live¶
| Item | What it is |
|---|---|
127.0.0.1:8000 |
Monitoring UI and API. |
~/.config/sushi/evidently/access.json |
Write token. Mode 0600. |
/var/lib/evidently/workspace |
Projects. They survive a service restart. |
/etc/evidently |
Service configuration. |
~/evidently-results/ |
Demo outputs, one directory per run. |
/opt/evidently/venv/bin/python |
Python with evidently installed. |
evidently.service |
The monitoring service. |
Your own tables¶
As ubuntu, use /opt/evidently/venv/bin/python with evidently.Report,
evidently.metrics.ValueDrift, and Pandas DataFrames. The installed
/opt/sushi/docs/README.md describes workspace access, exports, the token,
and Python examples.
Do not expose port 8000 on a public interface. Do not share the tunnel with someone who should not read the reports. There is no per-user role.
Token¶
sushi-evidently loads the token from the access file and does not print
it. A workstation client that must write should receive the token through
your own secret handling, not through a shell argument. Deleting demo files
does not remove the workspace report.
Last updated November 11, 2026 · Suggest an improvement