Route telemetry to the right backend — by label, environment, or tenant

Problem

Different telemetry belongs in different places, but a hard-wired pipeline sends everything to one destination regardless of what it is or who owns it.

LinkMesh

Define routes that match on labels, environment, source, or tenant, and send each stream to the destination that fits. One collector reads the rules LinkMesh renders and fans telemetry out accordingly — no per-team agent required.

Problem

A single processing pipeline treats every destination the same, even though what Splunk should receive and what object storage should receive are rarely identical.

LinkMesh

Each route carries its own chain of processors — filter, sample, mask, transform — so you can trim and redact for one destination while sending fuller records to another, all from the same collector.

Problem

Sending the same telemetry to two backends the naive way doubles storage and cost, and leaves two copies that drift apart over time.

LinkMesh

Fan a stream to more than one destination from a single route, with per-route filtering so each copy carries only what that backend needs — the security index gets the security fields, the archive gets the rest. One source, deliberate copies.

Problem

When one pipeline sends everything to a premium backend, low-value telemetry pays the same per-gigabyte price as the data you query every day.

LinkMesh

Route high-value logs to your primary backend and fan the rest to object storage or a cheaper OTLP destination — Grafana Loki, an archive bucket, anywhere. The split is a route rule, not a second collector.

Problem

Collectors coupled directly to one vendor make every backend change a fleet-wide rewrite, which is exactly how a cost or migration project stalls.

LinkMesh

Routes point at destinations you define centrally, built on standard OpenTelemetry Collectors and Grafana Alloy. Add, remove, or swap a backend by changing a route — the collectors keep running the open configuration they already have.

Problem

Without visibility into what flows where, a route change is a guess and a misrouted stream can go unnoticed until a backend bill or a missing dashboard surfaces it.

LinkMesh

The topology view shows every collector, route, and destination with live records-per-second measured on each connecting edge. You see which telemetry reaches which backend, at what rate, as it happens.

Problem

"Who changed where the payments logs go, when, and can we undo it?" should be a one-click answer, not an archaeology project across host configs.

LinkMesh

Every route, processor, and destination edit lands as a commit in the GitOps config repo — full diff, author, and timestamp. Roll back to any previous revision and re-push it to the fleet.