Dashboard
What the current dashboard exposes for database lifecycle, cluster settings, observability, and backups.
The dashboard is the main control-plane interface today.
Core database views
The current app groups database operations around:
- database detail views
- cluster sub-pages
- connect flow
- logs and metrics
- backups
- settings and API-key management
Cluster configuration tabs
The cluster area currently exposes dedicated sub-pages for:
- Instances
- Storage
- Parameters
- Change Data Capture
- Changes
Those pages queue workflows instead of mutating provider runtime directly in the browser.
Observability views
The dashboard currently includes:
- a metrics page with window selection and machine-scoped views
- a logs page with time-window presets, histogram navigation, and incremental streaming
- backup history and storage usage summaries
Read-model behavior
Some operator-facing history views are queue-backed read models rather than direct table reads. They are intentionally eventually consistent.
That matters most for:
- cluster changes history
- organization audit log surfaces
What the dashboard is not
The dashboard is not a complete external API manifest and it is not a public replacement for raw TigerBeetle tooling. It is the primary product console for current control-plane workflows.
For support boundaries and limitations, see TigerBeetle compatibility.