Skip to main content
Connectors are how OpenLIT attaches to data systems. Each connector is an atomic integration: one backend, one credential set, and a clear set of actions (test connection, validate AI telemetry, bind signals, manage secrets). Open the connectors experience from Organisation → Project → Connectors (Data sources). 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 are the long-term integration point in OpenLIT: data-source connectors today, with the same registry model expanding to notifications and other action types over time. Several read paths use portable @openplait adapters so query behavior stays consistent across backends.

Mental model

  • Atomic connectors — never a multi-backend blob. One Tempo instance, one Loki instance, one Prometheus endpoint.
  • Signal routing — each of traces / logs / metrics is bound independently. See Signal routing.
  • Database Config — ClickHouse lives as a Database Config and appears as the built-in connector. See Database Config.

Supported connectors (OpenLIT + OpenPlait)

These are the connectors available in open-source OpenLIT. OpenPlait packages power the portable query adapters for ClickHouse, Tempo, Loki, Prometheus, and Jaeger.

Built-in app store

Data-source connectors

Prometheus-compatible APIs (for example Grafana Mimir’s PromQL endpoint) use the Prometheus connector — there is no separate Mimir connector type in open-source OpenLIT.

Capability matrix

* Aggregate graphs are reconstructed in-process from a bounded sample of full traces when the backend cannot aggregate server-side.

Add a Jaeger connector in OpenLIT

Add source dialog with the connector type menu open, including Jaeger
  1. Select a project and environment in the header.
  2. Open Connectors and choose Add connector / Add source.
  3. Pick Jaeger from the connector type list.
  4. Set the Query URL (local all-in-one: http://localhost:16686) and auth if needed.
  5. Bind traces to the connector under signal routing.
Local demo credentials for seeded installs: email user@openlit.io, password openlituser. Jaeger all-in-one + seed script live in the OpenPlait adapter-jaeger integration folder.

Actions you can take on a connector

The connector registry is designed so actions attach to a connector type. Today’s data-source actions: Enterprise audit logs record connector create/update/delete/test plus bind/unbind (with signal, environment, and previous source when switching). RBAC permissions are connectors:read|create|update|delete|test|bind (owner/admin by default).

Future connector categories

The same registry will grow beyond datasources (for example notification and workflow connectors). Each new category still follows: atomic connector → credentials → actions → optional bindings. Data-source connectors remain the foundation for telemetry reads.

How OpenLIT finds AI telemetry

Backends hold all telemetry — not only AI. OpenLIT applies a layered AI selector so reads stay focused:
  • Resource telemetry.sdk.name = openlit
  • Resource telemetry.distro.name = openlit-cli
  • Any gen_ai.* attribute
  • coding_agent.session.id, or Claude Code session markers
  • Known coding_agent.* span names

Authentication cheat sheet

Security and reliability

  • Endpoints validated (http/https only); credentials in URLs rejected; private/metadata SSRF targets blocked where applicable.
  • Secrets live in Vault, redacted from errors, never logged.
  • Per-source concurrency caps, query budgets, short-lived cache + in-flight de-dupe, and backoff on transient 429/5xx.

OpenPlait packages

OpenLIT wraps these npm packages for portable reads: See the OpenPlait repository for publishing and adapter docs.

Signal routing

Bind traces, logs, and metrics independently.

Environments

Partition configs and connectors by environment.

Database Config

Env vars → ClickHouse Database Config.

Projects

How connectors are scoped to a project.