Stats Dashboard
Last updated Reviewed against Prism v0.3.26
What the Stats tab shows
| Panel | What it reports |
|---|---|
| Live TPS | A rolling 120-point throughput window, updated once per second during active requests. |
| Tokens per day | Stacked daily token totals, split by model or provider. |
| Tokens per month | Monthly totals for longer-range usage. |
| Session totals | Requests and tokens for the current run. |
| Client breakdown | Which clients are making requests, with a share-of-traffic chart. |
| TPS history | Throughput over time in 5-minute buckets, with adaptive ranges for longer windows. |
| By model | Requests, tokens and latency grouped by model. |
| Recent requests | The last 50 requests with model, client, token counts and timing. |
| Activity heatmap | A 365-day view of how often Prism was used. |
| Data management | A Clear All Stats action that empties the database. |
How clients are identified
Prism reads the User-Agent header and maps known clients to readable names. Recognised clients include Claude Code, Codex, Cursor, GitHub Copilot, Factory Droid, OpenCode, Empryo, Hermes, DeepSeek Harness, Aider, Continue, Supermaven, Windsurf and Trae. Anything unrecognised is recorded as its raw User-Agent string, or as "Unknown" when there is none.
X-Client-Name header with a request and Prism records that value instead. Useful for scripts and internal tools that want their own row in the breakdown.Where the data lives
Statistics are stored in stats.dbin Prism's per-user config directory, using SQLite in WAL mode. WAL keeps reads and writes from blocking each other and means the database survives an unclean shutdown.
# Windows %APPDATA%\prism\stats.db # macOS ~/Library/Application Support/prism/stats.db # Linux $XDG_CONFIG_HOME/prism/stats.db # default ~/.config/prism/stats.db
Privacy
Request and response bodies are never written to disk. The database holds metadata only: token counts, model names, detected client, timing and outcome. You can delete stats.db at any time and Prism recreates it on the next request.
Reading it directly
The database is ordinary SQLite, so custom reports are possible with any SQLite client. The admin UI's Stats tab is the supported view, and /v1/stats exposes the live snapshot as JSON for external dashboards.