Self-hostable collector for on-network capture.
Single Go binary inside your network. Local batching, on-disk buffering, redaction. Fans out to Trefur and any backends you already run, in parallel.
How it works.
The trefur collector is one Go binary. Run it on a host inside your network, in a Kubernetes sidecar, or as a systemd unit on a VM. Your SDKs point at it with the standard OTLP endpoints — /v1/traces, /v1/metrics, /v1/logs.
The collector batches locally, buffers to disk when the upstream drops, and replays cleanly when the network comes back. Redaction runs in the collector before egress — drop fields, mask substrings, hash identifiers — so sensitive content never leaves your perimeter unredacted.
The collector is fan-out friendly. Send traces to Trefur and any other OTLP backend in parallel. Keep your existing pipeline; add agent-aware observability without ripping anything out.
What you can do with it.
A minimal collector config.
Runs on.
Capture on your network. Send only what you mean to.
Free tier. The collector binary is free to download and run.