Skip to main content
OpenLIT lets you attach multiple Database Configs (ClickHouse connections) inside a project, each tagged with an environment. Use this to separate staging vs production data, tenants, or retention tiers without redeploying INIT_DB_* env vars. Day-2 connection changes belong in Organisation → Project → Database configurations / Connectors, not in live container env vars. See Database Config.

​
When to use this feature

  • Different environments — keep production and staging ClickHouse clusters on separate configs
  • Multi-tenancy — isolate datasets per customer while sharing one OpenLIT deployment
  • Centralized management — switch active Database Config from the header Databases control

​
Get started

OpenLIT database configuration list on a project
  1. Log in to OpenLIT (user@openlit.io / openlituser on local seed installs).
  2. Select organisation, project, and environment in the header.
  3. Open Organisation → Project → Database configurations (or Connectors → ClickHouse).
  4. Click Add, enter host, port, database, credentials, and environment.
  5. Save, then mark the config active for your user.
  6. Dashboards, requests, Prompt Hub, and Vault use the active Database Config for that project.
Pair each environment’s Database Config with signal routing when traces/logs/metrics live on Tempo, Loki, Prometheus, or Jaeger.

Database Config

Env vars → Database Config migration and field reference

Environments

How environments partition configs and connectors

Connectors

Data-source and memory connectors for OpenLIT