Destinations
Spanport is the pipe. Your Langfuse / Phoenix / Braintrust / Tempo backends stay the debugger of record.
Built-in adapters
| Type | Notes |
|---|---|
langfuse | OTLP/HTTP; auth via env:LANGFUSE or vaulted basic:pk:sk |
phoenix | OTLP/HTTP; env:PHOENIX or bearer:… |
braintrust | OTLP/HTTP; env:BRAINTRUST or bearer:… |
otlp_generic | Any OTLP/HTTP collector (Tempo, Honeycomb, Grafana, …) |
Wire-up
- Add a destination in the control plane (endpoint + optional auth).
- Secrets are sealed with
SPANPORT_VAULT_MASTER_KEYbefore persist — never returned on GET. - Create a route matching
swarm.id(or catch-all) with destination ids to fan out.
Operator detail: repo docs/destinations.md and docs/vault.md.
Privacy default
Destinations are per-project. For peer-org fan-out, enable redactContent on the route — shared correlation, split payloads.