Docs/Configuration/logging
OSS
logging
Where run output goes and how much of it. Every key here has a flag that overrides it for a single run.
Keys
The CLI and the Python client read root keys, not logging.level:
| Surface | Default | What it does |
|---|---|---|
--log-level / log_level / DBLIFT_LOG_LEVEL | info | debug, info, warn, error. |
--log-format / log_format / DBLIFT_LOG_FORMAT | text | text, json or html. There is no logging.format YAML key. |
--log-dir / log_dir / DBLIFT_LOG_DIR | logs | Directory for timestamped files. The CLI always has a default. |
--log-file / log_file | — | Write this single file instead of a timestamped name. |
A logging: YAML block can store level, file and directory, but the CLI does not consume logging.level for a run — it uses log_level and the flags above.
yaml
log_level: info
log_dir: "./logs"Every run writes Dblift_<schema>_<database>_<timestamp>.<ext> into the log directory — the extension follows --log-format — so concurrent runs against different databases never collide on one file.