Settings
Verification
Schedule verification runs, narrow them to tables, and turn the console button on or off.
What it proves and how to read a result: Data Verification.
Schedule
# docker-compose.yml, console service environment
BINTRAIL_CONSOLE_VERIFY_INTERVAL: 24h
BINTRAIL_CONSOLE_VERIFY_TABLES: shop.orders,shop.customers # optional| Setting | Values |
|---|---|
BINTRAIL_CONSOLE_VERIFY_INTERVAL (CLI: --verify-interval) | Hours or days: 6h, 24h, 7d. Minutes rejected. Unset = no schedule |
BINTRAIL_CONSOLE_VERIFY_TABLES (CLI: --verify-tables) | Comma-separated schema.table. Unset = every table |
Each interval, per server:
| Server has | Scheduled run |
|---|---|
| A backup location | Snapshot comparison |
| No backup location | Recovery-inputs check, so a schedule never does nothing |
| A manual run in flight | A skipped History entry |
History keeps the last 20 runs per server, across restarts.
Console button
On by default. VERIFY_TRIGGER=0 in the Compose .env turns it off; the page
then says "Verification from the console is turned off".
Snapshot modes also need a Backup dir or Backup S3 (Backup settings) and two snapshots (Backups → Create backup). Until then only the recovery-inputs check is enabled.
With DBTrail EE roles: operator or higher starts a run;
analyst and viewer read results.
Notifications
Webhook or Prometheus on a mismatch: Alerts.