Same agent Smaller bill. The tools and infrastructure to get more work from your AI. Fewer tokens. Less compute. Lower cost.
TypeScript agent-harnessagent-harness-engineeringai-engineeringai-observabilityamd-gpuclaude-codeclickhousecodexcoding-agentcoding-agentscursorgenaigpu-monitoringllm-observabilityllmopsnvidia-smiobservabilityopen-sourceopenaiopentelemetry
docs: add memory connector docs and reorganize connectors navigation (#1505)
Aman Agarwald6fbc57c4621
diff --git a/docs/docs.json b/docs/docs.jsonindex 041da143..d305b68d 100644--- a/docs/docs.json+++ b/docs/docs.json@@ -61,18 +61,20 @@"icon": "building","pages": ["latest/openlit/organisation/overview",- {- "group": "Projects",- "icon": "folder",- "pages": [- "latest/openlit/organisation/projects",- "latest/openlit/organisation/environments",- "latest/openlit/organisation/database-config",- "latest/openlit/organisation/connectors",- "latest/openlit/organisation/signal-routing",- "latest/openlit/organisation/telemetry-sources"- ]- }+ "latest/openlit/organisation/projects",+ "latest/openlit/organisation/environments",+ "latest/openlit/organisation/signal-routing",+ "latest/openlit/organisation/telemetry-sources",+ "latest/openlit/organisation/database-config"+ ]+ },+ {+ "group": "Connectors",+ "icon": "plug",+ "pages": [+ "latest/openlit/connectors/overview",+ "latest/openlit/connectors/datasource",+ "latest/openlit/connectors/memory"]}]diff --git a/docs/latest/openlit/configuration.mdx b/docs/latest/openlit/configuration.mdxindex d3fdb87e..d97f023c 100644--- a/docs/latest/openlit/configuration.mdx+++ b/docs/latest/openlit/configuration.mdx@@ -8,7 +8,7 @@ This guide covers environment variables for installing and fine-tuning OpenLIT.<Info>**ClickHouse connection at runtime is a [Database Config](/latest/openlit/organisation/database-config), not a live env lookup.**-`INIT_DB_*` variables **seed** the first Database Config when OpenLIT is first set up. Day-2 host, password, or environment changes belong in **Organisation → Database Config / Connectors**. See also [Connectors](/latest/openlit/organisation/connectors) and [Signal routing](/latest/openlit/organisation/signal-routing).+`INIT_DB_*` variables **seed** the first Database Config when OpenLIT is first set up. Day-2 host, password, or environment changes belong in **Organisation → Database Config** and **Connectors**. See also [Connectors](/latest/openlit/connectors/overview) and [Signal routing](/latest/openlit/organisation/signal-routing).</Info>## ClickHouse bootstrap (`INIT_DB_*`)diff --git a/docs/latest/openlit/organisation/connectors.mdx b/docs/latest/openlit/connectors/datasource.mdxsimilarity index 66%rename from docs/latest/openlit/organisation/connectors.mdxrename to docs/latest/openlit/connectors/datasource.mdxindex c8a3e4f1..031f1011 100644--- a/docs/latest/openlit/organisation/connectors.mdx+++ b/docs/latest/openlit/connectors/datasource.mdx@@ -1,20 +1,16 @@----title: 'Connectors'-sidebarTitle: 'Connectors'-description: 'Connect OpenLIT to ClickHouse and OpenPlait-backed observability backends — atomic connectors, actions, and the roadmap for a unified connector registry'-icon: 'plug'+title: 'Data-source connectors'+sidebarTitle: 'Data sources'+description: 'Connect OpenLIT to ClickHouse and OpenPlait-backed observability backends — atomic connectors, signal bindings, and portable query adapters'+icon: 'database'----**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).+**Data-source connectors** attach OpenLIT to observability backends for reading traces, logs, and metrics. Each connector is atomic: one Tempo instance, one Loki instance, one Prometheus endpoint.-Open the connectors experience from **Organisation → Project → Connectors** (Data sources). Always select the correct [project](/latest/openlit/organisation/projects) and [environment](/latest/openlit/organisation/environments) first — connectors belong to the project, not the organisation root.--<Frame>- <img src="/images/organisation/connectors-list.png" alt="OpenLIT Connectors page showing configured connectors and the connector catalog" />-</Frame>+Configure them from **Configuration → Connectors** (`/connectors`) or manage bindings from **Organisation → Project → Connectors**. Select the correct [project](/latest/openlit/organisation/projects) and [environment](/latest/openlit/organisation/environments) before adding or binding connectors.<Info>-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](https://github.com/openlit/openplait) adapters so query behavior stays consistent across backends.+Several read paths use portable [@openplait](https://github.com/openlit/openplait) adapters so query behavior stays consistent across backends. See the [Connectors overview](/latest/openlit/connectors/overview) for memory connectors and shared registry concepts.</Info>## Mental model@@ -44,17 +40,17 @@ flowchart LR## 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.+These are the data-source connectors available in open-source OpenLIT. OpenPlait packages power the portable query adapters for ClickHouse, Tempo, Loki, Prometheus, and Jaeger.### Built-in app store-| Connector | Package / implementation | Signals | What it’s for |+| Connector | Package / implementation | Signals | What it's for || --- | --- | --- | --- || **ClickHouse** | Database Config + `@openplait/adapter-clickhouse` | traces, logs, metrics (+ intelligence) | Default store; full correlation, raw SQL, evals metadata, vault |-### Data-source connectors+### External data-source connectors-| Connector | Package / implementation | Signals | What it’s for |+| Connector | Package / implementation | Signals | What it's for || --- | --- | --- | --- || **Grafana Tempo** | `@openplait/adapter-tempo` | traces | TraceQL search, trace tree, span events || **Grafana Loki** | `@openplait/adapter-loki` | logs | LogQL logs; correlate by trace id / service |@@ -62,7 +58,7 @@ These are the connectors available in open-source OpenLIT. OpenPlait packages po| **Jaeger** | `@openplait/adapter-jaeger` | traces | Jaeger Query HTTP API; sampled in-process aggregates |<Tip>-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.+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.</Tip>## Capability matrix@@ -77,17 +73,29 @@ Prometheus-compatible APIs (for example Grafana Mimir’s PromQL endpoint) use t\* 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 a Jaeger connector<Frame><img src="/images/organisation/openlit-jaeger-connector.png" alt="Add source dialog with the connector type menu open, including Jaeger" /></Frame>-1. Select a [project](/latest/openlit/organisation/projects) 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](/latest/openlit/organisation/signal-routing).+<Steps>+ <Step title="Select project and environment">+ Use the header selectors to pick the [project](/latest/openlit/organisation/projects) and [environment](/latest/openlit/organisation/environments).+ </Step>+ <Step title="Open Connectors">+ Go to **Configuration → Connectors** and choose **Add connector** / **Add source**.+ </Step>+ <Step title="Pick Jaeger">+ Select **Jaeger** from the data-source connector list.+ </Step>+ <Step title="Configure endpoint">+ Set the Query URL (local all-in-one: `http://localhost:16686`) and auth if needed.+ </Step>+ <Step title="Bind traces">+ Bind **traces** to the connector under [signal routing](/latest/openlit/organisation/signal-routing).+ </Step>+</Steps><Tip>Local demo credentials for seeded installs: email `[email protected]`, password `openlituser`. Jaeger all-in-one + seed script live in the OpenPlait `adapter-jaeger` integration folder.@@ -95,7 +103,7 @@ Local demo credentials for seeded installs: email `[email protected]`, password `o## Actions you can take on a connector-The connector registry is designed so **actions** attach to a connector type. Today’s data-source actions:+The connector registry is designed so **actions** attach to a connector type. Today's data-source actions:| Action | When to use it || --- | --- |@@ -108,11 +116,7 @@ The connector registry is designed so **actions** attach to a connector type. To| **Mark Database Config active** | Choose which ClickHouse app store the UI uses || **Share Database Config** | Grant edit / delete / re-share on a ClickHouse connection |-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.+Enterprise audit logs record connector create/update/delete/test plus bind/unbind (with signal, environment, and previous source when switching).## How OpenLIT finds AI telemetry@@ -158,16 +162,16 @@ See the [OpenPlait repository](https://github.com/openlit/openplait) for publish## Related<CardGroup cols={2}>+ <Card title="Memory connectors" href="/latest/openlit/connectors/memory" icon="brain">+ Claude, Mem0, and Zep for agent memory.+ </Card><Card title="Signal routing" href="/latest/openlit/organisation/signal-routing" icon="route">Bind traces, logs, and metrics independently.</Card>- <Card title="Environments" href="/latest/openlit/organisation/environments" icon="layer-group">- Partition configs and connectors by environment.- </Card><Card title="Database Config" href="/latest/openlit/organisation/database-config" icon="database">Env vars → ClickHouse Database Config.</Card>- <Card title="Projects" href="/latest/openlit/organisation/projects" icon="folder">- How connectors are scoped to a project.+ <Card title="Connectors overview" href="/latest/openlit/connectors/overview" icon="plug">+ Shared connector model and project scope.</Card></CardGroup>diff --git a/docs/latest/openlit/connectors/memory.mdx b/docs/latest/openlit/connectors/memory.mdxnew file mode 100644index 00000000..59571cf2--- /dev/null+++ b/docs/latest/openlit/connectors/memory.mdx@@ -0,0 +1,166 @@+---+title: 'Memory connectors'+sidebarTitle: 'Memory'+description: 'Connect OpenLIT to Claude, Mem0, and Zep memory stores — browse, search, write, copy, and ask Otter about agent memories'+icon: 'brain'+---++**Memory connectors** attach OpenLIT to external agent memory providers. Use them to browse stored facts, search semantically, add or edit memories, copy between backends, and ask **Otter** questions grounded in connector data.++Add memory connectors from **Configuration → Connectors** (`/connectors`) under the **Memory** category, or directly from the **Memory** page (`/memory`) when no connector exists yet. Connectors are scoped to the current [project](/latest/openlit/organisation/projects) and [environment](/latest/openlit/organisation/environments).++<Info>+Memory connectors use the same atomic registry as [data-source connectors](/latest/openlit/connectors/datasource), but they do not participate in telemetry signal routing. Credentials are encrypted on the connector instance rather than the ClickHouse vault.+</Info>++## Mental model++```mermaid+flowchart LR+ subgraph proj [Project + environment]+ MC[Memory connector]+ end+ MC --> API[Vendor memory API]+ MC --> MemPage[Memory page]+ MC --> Otter[Otter chat tools]+ MemPage --> Browse[List / graph / detail]+ Otter --> Tools[list / search / add / update / delete]+```++- **Atomic connectors** — one Mem0 project endpoint, one Zep tenant, one Claude memory store configuration per connector instance.+- **Capability-driven UI** — each vendor advertises supported operations (`list`, `search`, `add`, `update`, `delete`, `feedback`). OpenLIT hides actions the vendor does not support.+- **Filters** — user, session/run, and agent filters are declared per vendor. Some connectors require a session or user before listing memories.+- **Port links** — copying a memory to another connector stores provenance metadata so you can trace copies back to the source.++## Supported memory connectors++| Connector | Default endpoint | What it's for |+| --- | --- | --- |+| **Claude** | `https://api.anthropic.com` | Browse and edit memories in Anthropic Claude memory stores (Managed Agents memory beta) |+| **Mem0** | `https://api.mem0.ai` | Store and search long-term agent memories scoped by user, run, or agent |+| **Zep** | `https://api.getzep.com` | Session memory and knowledge-graph facts for agents |++Self-hosted Mem0 or Zep deployments work when you point the connector at a compatible API URL and supply the same authentication style as the hosted service.++## Capability matrix++| Connector | List | Search | Get | Add | Update | Delete | Feedback | Required filters |+| --- | --- | --- | --- | --- | --- | --- | --- | --- |+| **Claude** | Yes | Yes* | Yes | Yes | Yes | Yes | No | Memory store (session) |+| **Mem0** | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Optional user / run / agent |+| **Zep** | Yes | Yes | Yes | Yes | No | Yes† | No | User; session required for writes |++\* Claude has no dedicated search API — OpenLIT filters listed memories locally for search queries.++† Zep delete targets graph edges/nodes, not an entire session.++## Add a memory connector++<Steps>+ <Step title="Select project and environment">+ Use the header selectors for the target [project](/latest/openlit/organisation/projects) and [environment](/latest/openlit/organisation/environments).+ </Step>+ <Step title="Open Connectors">+ Go to **Configuration → Connectors**, open the **Memory** section in the catalog, and choose **Add connector**.+ </Step>+ <Step title="Pick a vendor">+ Select **Claude**, **Mem0**, or **Zep**.+ </Step>+ <Step title="Configure endpoint and credentials">+ Set the API URL (defaults work for hosted services), optional SSRF toggles for private networks, and the API key. Mem0 also accepts optional organization and project IDs.+ </Step>+ <Step title="Test and save">+ Run a health check, then save. Open **Memory** (`/memory`) and select the connector from the dropdown.+ </Step>+</Steps>++<Tip>+You can also add a connector from the Memory page empty state — **Add memory connector** opens the same add dialog.+</Tip>++## Memory page features++Once a connector is configured, the **Memory** page provides:++| Feature | Description |+| --- | --- |+| **Connector selector** | Switch between memory connectors in the current environment |+| **Filters** | User, session/run, and agent filters when the vendor supports them |+| **Memory list** | Paginated list with search |+| **Detail sheet** | Full memory content, metadata, history, and feedback (when supported) |+| **Graph view** | Relationship visualization for graph-capable vendors (for example Zep) |+| **Write actions** | Add, update, or delete memories when the connector advertises those capabilities |+| **Copy** | Copy selected memories to another write-capable connector in the same environment |+| **Ask Otter** | Natural-language search and Q&A grounded in connector list/search APIs |++## Otter memory tools++When Otter runs on the Memory page or in chat with memory context, it can call connector-backed tools:++| Tool | When available |+| --- | --- |+| `list_memories` | Connector supports `list` |+| `search_memories` | Connector supports `search` |+| `add_memory` | Connector supports `add` |+| `update_memory` | Connector supports `update` |+| `delete_memory` | Connector supports `delete` |++Otter passes required filter arguments (user, session, agent) when the vendor mandates them. Enterprise builds apply the same RBAC and audit hooks as the `/api/memory` routes.++## Authentication++| Connector | Auth style | Notes |+| --- | --- | --- |+| **Claude** | API key (`x-api-key`) | Sends the `agent-memory-2026-07-22` beta header for memory store APIs |+| **Mem0** | Token (`Authorization: Token <apiKey>`) | Works with Mem0 Platform or self-hosted compatible endpoints |+| **Zep** | API key (`Authorization: Api-Key <apiKey>`) | Works with Zep Cloud or self-hosted compatible endpoints |++API keys are stored encrypted on the connector (`enc:v1:…`) and decrypted only server-side for outbound requests.++## Copy between connectors++Use **Copy** on the Memory page to duplicate memories into another write-capable connector in the same project and environment. OpenLIT:++1. Reads the source memory from the origin connector+2. Writes to the destination connector when `add` is supported+3. Stores `metadata.openlit.port` on the destination memory and links the destination connector back to the source for traceability++Copy requires `connectors:update` (or equivalent memory mutation permission in enterprise).++## Security and reliability++- Endpoints validated (`http`/`https` only); credentials in URLs rejected; private/metadata SSRF targets blocked where applicable.+- Secrets encrypted on the connector instance, redacted from errors, never logged.+- Outbound calls use the shared safe-fetch layer with the same SSRF controls as data-source connectors.+- Content limits: memory body up to 20,000 characters; metadata JSON up to 4,000 characters.++## Vendor documentation++<CardGroup cols={3}>+ <Card title="Claude memory" href="https://platform.claude.com/docs/en/managed-agents/memory" icon="book">+ Anthropic Managed Agents memory stores.+ </Card>+ <Card title="Mem0 API" href="https://docs.mem0.ai/api-reference" icon="book">+ Mem0 Platform REST API reference.+ </Card>+ <Card title="Zep SDK" href="https://help.getzep.com/sdk-reference" icon="book">+ Zep Cloud API and graph memory.+ </Card>+</CardGroup>++## Related++<CardGroup cols={2}>+ <Card title="Connectors overview" href="/latest/openlit/connectors/overview" icon="plug">+ Shared connector registry and project scope.+ </Card>+ <Card title="Data-source connectors" href="/latest/openlit/connectors/datasource" icon="database">+ Tempo, Loki, Prometheus, Jaeger, and ClickHouse.+ </Card>+ <Card title="Otter (AI Copilot)" href="/latest/openlit/chat" icon="message">+ Chat with Otter across OpenLIT surfaces.+ </Card>+ <Card title="Environments" href="/latest/openlit/organisation/environments" icon="layer-group">+ Partition memory connectors by environment.+ </Card>+</CardGroup>diff --git a/docs/latest/openlit/connectors/overview.mdx b/docs/latest/openlit/connectors/overview.mdxnew file mode 100644index 00000000..636ca858--- /dev/null+++ b/docs/latest/openlit/connectors/overview.mdx@@ -0,0 +1,85 @@+---+title: 'Connectors'+sidebarTitle: 'Overview'+description: 'Atomic integrations that connect OpenLIT to observability backends and external memory providers — scoped to projects and environments'+icon: 'plug'+---++**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](/latest/openlit/organisation/projects) and [environment](/latest/openlit/organisation/environments) first — connectors belong to the project, not the organisation root.++<Frame>+ <img src="/images/organisation/connectors-list.png" alt="OpenLIT Connectors page showing configured connectors and the connector catalog" />+</Frame>++<Info>+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.+</Info>++## Connector categories++<CardGroup cols={2}>+ <Card title="Data-source connectors" href="/latest/openlit/connectors/datasource" icon="database">+ ClickHouse, Tempo, Loki, Prometheus, and Jaeger — read traces, logs, and metrics with per-signal routing.+ </Card>+ <Card title="Memory connectors" href="/latest/openlit/connectors/memory" icon="brain">+ Claude, Mem0, and Zep — browse, search, write, and copy agent memories from the Memory page and Otter.+ </Card>+</CardGroup>++## Mental model++```mermaid+flowchart LR+ subgraph org [Organisation]+ proj[Project]+ end+ subgraph env [Environment]+ bindT[traces binding]+ bindL[logs binding]+ bindM[metrics binding]+ mem[memory connectors]+ end+ proj --> env+ bindT --> DS1[Tempo]+ bindL --> DS2[Loki]+ bindM --> DS3[Prometheus]+ mem --> M1[Mem0]+ mem --> M2[Zep]+```++- **Atomic connectors** — one backend per connector instance. Never a multi-backend blob.+- **Project scope** — connectors are created on a project and partitioned by [environment](/latest/openlit/organisation/environments).+- **Data-source bindings** — traces, logs, and metrics bind independently. See [Signal routing](/latest/openlit/organisation/signal-routing).+- **Memory usage** — memory connectors power the **Memory** page (`/memory`) and Otter memory tools; they do not replace telemetry routing.++## Common actions++| Action | Data-source | Memory |+| --- | --- | --- |+| Add / edit connector | Yes | Yes |+| Store credentials | Vault (ClickHouse) or connector secret | Encrypted on connector |+| Health check / test connection | Yes | Yes |+| Validate AI signal | Yes (`gen_ai.*` markers) | — |+| Bind signal | traces / logs / metrics | — |+| Browse / search / write memories | — | Yes (capability-dependent) |++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).++## Related++<CardGroup cols={2}>+ <Card title="Organisation overview" href="/latest/openlit/organisation/overview" icon="building">+ How projects and environments scope connectors.+ </Card>+ <Card title="Signal routing" href="/latest/openlit/organisation/signal-routing" icon="route">+ Bind traces, logs, and metrics to data-source connectors.+ </Card>+ <Card title="Database Config" href="/latest/openlit/organisation/database-config" icon="database">+ ClickHouse app store and built-in connector.+ </Card>+ <Card title="Environments" href="/latest/openlit/organisation/environments" icon="layer-group">+ Partition connectors by environment.+ </Card>+</CardGroup>diff --git a/docs/latest/openlit/developer-resources/multiple-db.mdx b/docs/latest/openlit/developer-resources/multiple-db.mdxindex e3c7da12..562d6935 100644--- a/docs/latest/openlit/developer-resources/multiple-db.mdx+++ b/docs/latest/openlit/developer-resources/multiple-db.mdx@@ -40,7 +40,7 @@ Pair each environment’s Database Config with [signal routing](/latest/openlit/<Card title="Environments" href="/latest/openlit/organisation/environments" icon="layer-group">How environments partition configs and connectors</Card>- <Card title="Connectors" href="/latest/openlit/organisation/connectors" icon="plug">- External data-source connectors for OpenLIT+ <Card title="Connectors" href="/latest/openlit/connectors/overview" icon="plug">+ Data-source and memory connectors for OpenLIT</Card></CardGroup>diff --git a/docs/latest/openlit/organisation/database-config.mdx b/docs/latest/openlit/organisation/database-config.mdxindex daf8db8c..ac3eec1c 100644--- a/docs/latest/openlit/organisation/database-config.mdx+++ b/docs/latest/openlit/organisation/database-config.mdx@@ -40,7 +40,7 @@ A **Database Config** is the ClickHouse connection OpenLIT uses as its **app sto4. Optionally keep `INIT_DB_*` in Compose only so **new** installs still seed a default — do not rely on them for day-2 connection changes.<Warning>-OpenLIT still requires a Database Config even when raw traces/logs/metrics are routed to Tempo, Loki, Prometheus, Datadog, or other [connectors](/latest/openlit/organisation/connectors). Evaluations, boards metadata, rules, vault secrets, and agent summaries stay in ClickHouse.+OpenLIT still requires a Database Config even when raw traces/logs/metrics are routed to Tempo, Loki, Prometheus, Datadog, or other [data-source connectors](/latest/openlit/connectors/datasource). Evaluations, boards metadata, rules, vault secrets, and agent summaries stay in ClickHouse.</Warning>## Add a database configuration@@ -123,8 +123,8 @@ A Database Config can be shared with teammates by email with separate **edit**,</AccordionGroup><CardGroup cols={2}>- <Card title="Connectors" href="/latest/openlit/organisation/connectors" icon="plug">- Catalog of data-source connectors and actions.+ <Card title="Connectors" href="/latest/openlit/connectors/overview" icon="plug">+ Data-source and memory connectors and actions.</Card><Card title="Configuration reference" href="/latest/openlit/configuration" icon="sliders">Full list of bootstrap and OAuth environment variables.diff --git a/docs/latest/openlit/organisation/environments.mdx b/docs/latest/openlit/organisation/environments.mdxindex a80cc6d2..37ea0894 100644--- a/docs/latest/openlit/organisation/environments.mdx+++ b/docs/latest/openlit/organisation/environments.mdx@@ -48,7 +48,7 @@ Environments are created when you add a Database Config or connector with a newSelect an existing environment, or enter a new name when adding a Database Config / connector.</Step><Step title="Attach resources">- Add a [Database Config](/latest/openlit/organisation/database-config) and optional [connectors](/latest/openlit/organisation/connectors) for that environment.+ Add a [Database Config](/latest/openlit/organisation/database-config) and optional [connectors](/latest/openlit/connectors/overview) for that environment.</Step><Step title="Bind signals">Use [signal routing](/latest/openlit/organisation/signal-routing) so traces, logs, and metrics resolve to the right connector for this environment.@@ -67,8 +67,8 @@ Environments are created when you add a Database Config or connector with a new<Card title="Database Config" href="/latest/openlit/organisation/database-config" icon="database">Env vars → ClickHouse Database Config per environment.</Card>- <Card title="Connectors" href="/latest/openlit/organisation/connectors" icon="plug">- Data-source connectors available in OpenLIT.+ <Card title="Connectors" href="/latest/openlit/connectors/overview" icon="plug">+ Data-source and memory connectors in OpenLIT.</Card><Card title="Signal routing" href="/latest/openlit/organisation/signal-routing" icon="route">Bind traces, logs, and metrics per environment.diff --git a/docs/latest/openlit/organisation/overview.mdx b/docs/latest/openlit/organisation/overview.mdxindex 0c8a61f7..b0e9eb14 100644--- a/docs/latest/openlit/organisation/overview.mdx+++ b/docs/latest/openlit/organisation/overview.mdx@@ -4,14 +4,14 @@ description: 'Organisation → Project → Environment → Database Config and cicon: 'building'----Organisations in OpenLIT are shared workspaces for teams. Inside an organisation, **projects** own everything you configure for telemetry backends: environments, Database Configs, connectors, and signal bindings.+Organisations in OpenLIT are shared workspaces for teams. Inside an organisation, **projects** own everything you configure for telemetry and memory: environments, Database Configs, connectors, and signal bindings.```textOrganisation└── Project ← create / select a project first└── Environment├── Database Config (ClickHouse app store)- ├── Connectors (Tempo, Loki, Prometheus, Jaeger)+ ├── Connectors (data sources + memory)└── Signal routing (traces / logs / metrics)```@@ -41,8 +41,8 @@ Every organisation has a default project. Existing installations are mapped to a<Card title="Database Config" href="/latest/openlit/organisation/database-config" icon="database">Add ClickHouse on a project (seeded from INIT_DB_* then managed in the UI).</Card>- <Card title="Connectors" href="/latest/openlit/organisation/connectors" icon="plug">- Attach Tempo, Loki, Prometheus, or Jaeger on a project.+ <Card title="Connectors" href="/latest/openlit/connectors/overview" icon="plug">+ Data-source and memory connectors on a project.</Card><Card title="Signal routing" href="/latest/openlit/organisation/signal-routing" icon="route">Bind traces, logs, and metrics independently per environment.diff --git a/docs/latest/openlit/organisation/projects.mdx b/docs/latest/openlit/organisation/projects.mdxindex 08338693..bbc344ef 100644--- a/docs/latest/openlit/organisation/projects.mdx+++ b/docs/latest/openlit/organisation/projects.mdx@@ -5,14 +5,14 @@ sidebarTitle: 'Projects'icon: 'folder'----Everything under **Organisation → Projects** is project-scoped. You create a project first; then that project owns environments, ClickHouse **Database Configs**, data-source **connectors** (Tempo, Loki, Prometheus, Jaeger), and **signal routing**.+Everything under **Organisation → Projects** is project-scoped. You create a project first; then that project owns environments, ClickHouse **Database Configs**, **connectors** (data sources and memory), and **signal routing**.```textOrganisation└── Project ← create this first├── Environments├── Database Configs (ClickHouse)- ├── Connectors (Tempo / Loki / Prometheus / Jaeger)+ ├── Connectors (data sources + memory)└── Signal routing```@@ -57,7 +57,7 @@ Use **environments** (`production`, `staging`, …) inside a project when you ne| --- | --- || **Environments** | Named partitions (`production`, `staging`, …) || **Database Configs** | ClickHouse app-store connections per environment |-| **Connectors** | Tempo, Loki, Prometheus, Jaeger (and ClickHouse as built-in) |+| **Connectors** | Data-source (Tempo, Loki, Prometheus, Jaeger, ClickHouse) and memory (Claude, Mem0, Zep) || **Signal bindings** | Which connector serves traces / logs / metrics per environment |<Frame>@@ -77,8 +77,8 @@ Project access controls which organisation members can use a project. Existing o<Card title="Database Config" href="/latest/openlit/organisation/database-config" icon="database">Add ClickHouse connections on the project.</Card>- <Card title="Connectors" href="/latest/openlit/organisation/connectors" icon="plug">- Attach Tempo, Loki, Prometheus, or Jaeger.+ <Card title="Connectors" href="/latest/openlit/connectors/overview" icon="plug">+ Data-source and memory connectors on the project.</Card><Card title="Signal routing" href="/latest/openlit/organisation/signal-routing" icon="route">Bind traces, logs, and metrics per environment.diff --git a/docs/latest/openlit/organisation/signal-routing.mdx b/docs/latest/openlit/organisation/signal-routing.mdxindex 1988f574..cf60bdd7 100644--- a/docs/latest/openlit/organisation/signal-routing.mdx+++ b/docs/latest/openlit/organisation/signal-routing.mdx@@ -5,7 +5,7 @@ description: 'Route traces, logs, and metrics to different OpenLIT connectors peicon: 'route'----**Signal routing** decides which [connector](/latest/openlit/organisation/connectors) serves each telemetry signal for a project [environment](/latest/openlit/organisation/environments). Bindings are independent: traces can come from Tempo while logs come from Loki and metrics from Prometheus — in the same OpenLIT project.+**Signal routing** decides which [data-source connector](/latest/openlit/connectors/datasource) serves each telemetry signal for a project [environment](/latest/openlit/organisation/environments). Bindings are independent: traces can come from Tempo while logs come from Loki and metrics from Prometheus — in the same OpenLIT project.## Signals@@ -113,8 +113,8 @@ Binding and unbinding are written to the organisation **audit log** (`connectors## Related<CardGroup cols={2}>- <Card title="Connectors catalog" href="/latest/openlit/organisation/connectors" icon="plug">- Supported OpenLIT + OpenPlait connectors and actions.+ <Card title="Connectors catalog" href="/latest/openlit/connectors/datasource" icon="plug">+ Supported OpenLIT + OpenPlait data-source connectors and actions.</Card><Card title="Environments" href="/latest/openlit/organisation/environments" icon="layer-group">How bindings are partitioned by environment.diff --git a/docs/latest/openlit/organisation/telemetry-sources.mdx b/docs/latest/openlit/organisation/telemetry-sources.mdxindex 0e8a504c..30c4f358 100644--- a/docs/latest/openlit/organisation/telemetry-sources.mdx+++ b/docs/latest/openlit/organisation/telemetry-sources.mdx@@ -8,7 +8,7 @@ icon: 'plug'**Telemetry Sources** is the same product surface as **Connectors**. Prefer the connectors and signal-routing guides below — they match the OpenLIT dashboard language (connectors, actions, and per-signal routing).<CardGroup cols={2}>- <Card title="Connectors" href="/latest/openlit/organisation/connectors" icon="plug">+ <Card title="Connectors" href="/latest/openlit/connectors/datasource" icon="plug">Catalog of supported OpenLIT + OpenPlait data-source connectors and actions.</Card><Card title="Signal routing" href="/latest/openlit/organisation/signal-routing" icon="route">@@ -26,4 +26,4 @@ icon: 'plug'OpenLIT reads raw traces, logs, and metrics from the built-in ClickHouse store by default. You can attach external backends supported in open-source OpenLIT — **Tempo**, **Loki**, **Prometheus**, and **Jaeger** — and bind each signal independently per [environment](/latest/openlit/organisation/environments). Derived intelligence always stays in ClickHouse via [Database Config](/latest/openlit/organisation/database-config).-For auth tables, AI selectors, correlation limits, and reliability hardening, see the [Connectors](/latest/openlit/organisation/connectors) page — that document is the canonical reference.+For auth tables, AI selectors, correlation limits, and reliability hardening, see [Data-source connectors](/latest/openlit/connectors/datasource) — that document is the canonical reference for telemetry backends.diff --git a/src/client/src/constants/documentation-links.ts b/src/client/src/constants/documentation-links.tsindex 1c8ade7c..6ccf6b44 100644--- a/src/client/src/constants/documentation-links.ts+++ b/src/client/src/constants/documentation-links.ts@@ -5,7 +5,9 @@ const DOCUMENTATION_LINKS = {multipleDb: "https://docs.openlit.io/latest/openlit/developer-resources/multiple-db",databaseConfig: "https://docs.openlit.io/latest/openlit/organisation/database-config",environments: "https://docs.openlit.io/latest/openlit/organisation/environments",- connectors: "https://docs.openlit.io/latest/openlit/organisation/connectors",+ connectors: "https://docs.openlit.io/latest/openlit/connectors/overview",+ memoryConnectors: "https://docs.openlit.io/latest/openlit/connectors/memory",+ datasourceConnectors: "https://docs.openlit.io/latest/openlit/connectors/datasource",signalRouting: "https://docs.openlit.io/latest/openlit/organisation/signal-routing",telemetrySources: "https://docs.openlit.io/latest/openlit/organisation/telemetry-sources",anonymousTelemetry: "https://docs.openlit.io/latest/openlit/developer-resources/anonymous-telemetry",