Skip to main content

​
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

  1. 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.
  2. Settings → Integrations → This tenant → Telemetry export (OTLP) → Configure:
  1. 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.
  • 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.