Skip to main content
Connectors are how OpenLIT attaches to external systems. Each connector is an atomic integration: one backend, one credential set, and a clear set of actions (test connection, validate signals, bind telemetry, browse memories, and more). Open Connectors from the sidebar under Configuration → Connectors (/connectors). Always select the correct project and environment first — connectors belong to the project, not the organisation root.
OpenLIT Connectors page showing configured connectors and the connector catalog
Connectors share one registry model across categories. Data-source connectors route telemetry reads; memory connectors connect OpenLIT to agent memory stores for browsing, editing, and Otter-powered search.

​
Connector categories

Data-source connectors

ClickHouse, Tempo, Loki, Prometheus, and Jaeger — read traces, logs, and metrics with per-signal routing.

Memory connectors

Claude, Mem0, and Zep — browse, search, write, and copy agent memories from the Memory page and Otter.

​
Mental model

  • Atomic connectors — one backend per connector instance. Never a multi-backend blob.
  • Project scope — connectors are created on a project and partitioned by environment.
  • Data-source bindings — traces, logs, and metrics bind independently. See Signal routing.
  • Memory usage — memory connectors power the Memory page (/memory) and Otter memory tools; they do not replace telemetry routing.

​
Common actions

Enterprise audit logs record connector create, update, delete, test, bind, and unbind events. RBAC permissions are connectors:read|create|update|delete|test|bind (owner/admin by default).

Organisation overview

How projects and environments scope connectors.

Signal routing

Bind traces, logs, and metrics to data-source connectors.

Database Config

ClickHouse app store and built-in connector.

Environments

Partition connectors by environment.