Telemetry Export (OTLP, per workspace)
Every request KnoxCall proxies for your workspace, and the request-count and latency metrics derived from them, can be streamed to a collector you run — Datadog, Grafana, Splunk, SigNoz, Elastic, or an OpenTelemetry Collector in front of anything. Only your workspace’s records ship to it; there is no operator data in the stream and no other workspace’s. Scope: This tenant. There is no platform default; each workspace configures its own destination.What ships
No traces. Traces belong to the operator export, because a trace spans the whole platform.
1. Configure
- Mint a write-only ingest credential at your backend and find its OTLP/HTTP base endpoint. The values are identical to the operator export’s — use the recipes for Grafana Cloud, Honeycomb, New Relic, Datadog, SigNoz, Elastic, Axiom and a self-run Collector.
- Settings → Integrations → This tenant → Telemetry export (OTLP) → Configure:
- Save. Applies on the next request — no restart.
2. Verify
Make a request through one of your routes. The log record arrives within the batch interval (a few seconds); the first metric point on the next 60-second tick.Things that bite
- Base endpoint only — never a URL that already ends in
/v1/logs. No?query, no#fragmentand nouser:password@in it: KnoxCall appends the signal path, and credentials belong in OTLP auth headers, which are stored encrypted. - Public destinations only. The endpoint must resolve only to public addresses. Loopback, private ranges (10/8, 172.16/12, 192.168/16, 100.64/10), link-local and the cloud metadata address, and KnoxCall’s own hosts are refused when you save, and again every time KnoxCall opens a connection, so a name that later changes to a private address stops receiving exports. A workspace export cannot reach a collector on a private network, including on a self-hosted install. The operator export can.
- Redirects are not followed. A collector that answers with a redirect gets nothing more.
- Headers KnoxCall will not send:
Host,Content-Length,Cookie, hop-by-hop headers, the forwarding and client-IP family (X-Forwarded-*,Forwarded,X-Real-IP,True-Client-IP,CF-*), and anyX-KnoxCall-*orX-Knox-*header. These are refused on save. - Export must never affect your traffic, so a failing collector is not reported on the request path: a wrong token shows up as nothing arriving, not as an error in KnoxCall. Check the backend, then the headers.
- Changes propagate within about a minute across all gateway workers; the worker that took your save switches immediately.
- Disabling the row stops the stream; deleting it does too. There is no environment fallback for a workspace export.
Related
- OpenTelemetry export — signal contents and conventions
- OpenTelemetry export (operator) — the whole-gateway export, and the backend recipes
- Analytics — the same metrics in the dashboard