Skip to content

docs: a Loki tenant goes in the relay headers, not in Setup #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tsenart merged 1 commit into from
Oct 1, 2026
Merged

docs: a Loki tenant goes in the relay headers, not in Setup #11

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,8 +133,10 @@ Loki). In the **Endpoint** field enter:
relay://<upstream-name>
```

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:
Expand Down
Loading