Self-hosted telemetry pipeline software for OpenTelemetry

Problem

Hand-written collector config is hard to review and easy to break.

LinkMesh

Compose sources, processors and destinations in the visual pipeline builder. A pipeline is a reusable recipe — filter, transform, mask — that many routes can reference, so a change is made once. Every edit lands as a commit in a Git-versioned config repository with diff, author and rollback.

Problem

A processor chain is only proven once it has already run against production traffic.

LinkMesh

Capture a bounded sample of the live records on a route, keep it in the Sample Library, and dry-run any pipeline against it. You see the result of every step and the final output before you save.

Problem

A single hard-wired pipeline sends everything to one backend.

LinkMesh

Routes match on attributes, labels, environment, source or tenant with a guided field/operator/value builder, or raw OTTL when you need it. Each route carries its own processor chain and can fan out to several destinations — your primary backend, a cheaper OTLP store, Kafka or an archive bucket.

Problem

PII and secrets travel inside telemetry until a backend indexes them.

LinkMesh

Apply masking in the pipeline itself with built-in templates (card numbers, email and phone) or your own regex and OTTL rules, so the data is redacted before it leaves your network.

Problem

Without measurement, a pipeline change is a guess and a misrouted stream goes unnoticed.

LinkMesh

The topology view shows every collector, route and destination with live records per second on each connecting edge, plus health for every collector in the fleet.

Problem

Updating dozens of collectors one by one is slow, and some always get missed.

LinkMesh

Collector groups apply the same pipelines and routes to every member; a collector that joins a group picks them up automatically. Configuration is delivered over OpAMP to standard otelcol-contrib collectors, with no proprietary agent in the data path.

Problem

Pipeline platforms often hold your backend credentials and run the control plane in their cloud.

LinkMesh

LinkMesh is one binary with embedded storage, on a VM, in Docker or air-gapped. Backend tokens live in a built-in encrypted vault, referenced by name and substituted only at delivery, so they are never written to Git. Collectors authenticate with an enrollment token over TLS you terminate yourself.