dbt-logbook 0.5.0

Run history for dbt. Every invocation recorded, nothing overwritten.

dbt-logbook

Run history for dbt. Every invocation recorded, nothing overwritten.

dbt writes run_results.json and overwrites it on the next run. dbt-logbook keeps every run in a local SQLite store and gives you the views that history makes possible - with zero configuration and zero changes to your dbt project.

What you get

• Run timeline: every recorded invocation, status at a glance, failures inline
• Per-model history: duration sparkline across runs - see the regression the moment it starts, and the failed runs marked on the line
• What changed between two runs: checksum-based diff (added / removed / modified models), powered by dbt's own per-node checksums
• Lineage: clickable DAG from your manifest, tests hidden by default

Quickstart

uvx dbt-logbook demo          # populated playground, no dbt project needed

In a real dbt project (any adapter - DuckDB, Snowflake, SQL Server, Postgres, ...):

cd your-dbt-project
uvx dbt-logbook ui            # instant read-only UI over the artifacts dbt already wrote

History accrues from the capture wrapper - change one line in your cron/CI:

dbt-logbook exec -- dbt build     # runs dbt untouched, records the run
                                  # exit code passes through exactly

Or ingest artifacts from anywhere (for example, downloaded CI artifacts):

dbt-logbook import path/to/artifacts --env prod

Ask your agent about your runs (MCP)

The history store is exposed as an MCP server - the cross-run questions that current-state tools structurally can't answer, because dbt overwrites its artifacts:

claude mcp add dbt-logbook -- uvx dbt-logbook mcp     # from your dbt project dir

Then ask: "what broke last night?", "which models got slower this week?", "which tests are flaky?", "what changed between the last two runs?", "what would state:modified rebuild?". Full tool list and REST equivalents: docs/api-contract.md.

Run it as the platform (scheduler + alerts)

One process replaces cron + hope. Drop a dbt-logbook.yml in the project root:

schedules:
  hourly:
    cron: "0 * * * *"
    command: dbt build
    retries: 2
notify:
  slack_webhook: https://hooks.slack.com/services/...   # or teams_webhook
  on: [failure, recovery]

dbt-logbook serve

You get: cron scheduling with retries, every run recorded, a Slack/Teams ping on new failures and on recovery, auto-import of runs that happen outside the scheduler (a target/ watcher), and the UI - all one process, localhost only.

Keep it alive the boring way: docker run --restart unless-stopped ... or a systemd unit with Restart=on-failure.

Slim CI without artifact plumbing

The store already holds every environment's last-good manifest - serve it to CI instead of copying manifest.json to S3:

# in CI, against a reachable dbt-logbook serve --host ... --token ...
- run: |
    curl -sf -H "Authorization: Bearer $DBT_LOGBOOK_TOKEN" \
      "$LOGBOOK_URL/api/state/prod/manifest.json" -o ci-state/manifest.json
    dbt build --select state:modified --defer --state ci-state

Locally the same thing is one command: dbt-logbook state --env prod --out ci-state. Binding beyond localhost requires a token; /api/* then demands Authorization: Bearer <token>.

How it works

dbt-logbook reads only dbt's stable surfaces - the CLI and the artifact files (manifest.json, run_results.json) - and never imports dbt internals. That is why it works unchanged across dbt Core 1.7 through 2.0 (tested against golden artifacts of 1.7, 1.8, 1.10, 1.11, and 2.0-alpha), and why it needs no dbt installation of its own.

Every run's artifacts land in .dbtlogbook/history.db (SQLite; add .dbtlogbook/ to your project's .gitignore). Manifests are content-hashed and gzipped, so the store stays small. Failed dbt runs are captured too - those are the ones you'll want history for.

Platform notes

• macOS and Linux. On Windows, ui and import are untested but should work (pure Python); exec is unsupported for now (POSIX signal semantics).
• The UI binds to localhost only.

Health screen

#/health in the UI: duration regressions (latest vs median baseline), flaky nodes (status flips across recent runs), and source freshness over time (from dbt source freshness snapshots the watcher or wrapper picks up). Generated dbt docs output is served at /docs-site/ when present.

Roadmap

• Windows exec support, UI framework rebuild: see TODOS.md - both deferred until demand shows up in issues.

License: Apache-2.0. Not affiliated with dbt Labs; "dbt" is a trademark of dbt Labs, Inc.