From 3cbc77874a81c3f66d1db3ea39d08c2b2e413869 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tom=C3=A1s=20Senart?= Date: Wed, 30 Sep 2026 19:09:37 -0700 Subject: [PATCH] docs: a Loki tenant goes in the relay headers, not in Setup Perfloop refuses a tenant for a relay source, as it refuses a credential (proxy/telemetry_relay_test.go in perfloop/perfloop). Step 6 told the reader to enter it in Setup, which fails validation. The tenant belongs in the upstream's X-Scope-OrgID header, as docs/security.md already says. Co-Authored-By: Claude Fable 5.1 --- docs/setup.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/setup.md b/docs/setup.md index ddd440a..65b29d1 100644 --- a/docs/setup.md +++ b/docs/setup.md @@ -133,8 +133,10 @@ Loki). In the **Endpoint** field enter: relay:// ``` -Leave the credential empty; a relay source has none. For Loki, enter the -tenant id if your Loki is multi-tenant. Complete the connection. +Leave the credential empty, and for Loki leave the tenant empty too; Perfloop +refuses both for a relay source. A multi-tenant Loki takes its tenant from an +`X-Scope-OrgID` entry in the upstream's `headers` in `relay.yaml` (step 3). +Complete the connection. Checkpoint: Setup shows the source as connected, and the relay log shows the connection check as a read: