Manage your OpenTelemetry Collector fleet from one place

Problem

When every collector is edited by hand, they diverge. There is no single artifact you can point to and call "the fleet’s configuration".

LinkMesh

Define configuration once — per group, per environment — and LinkMesh renders and pushes the same effective config to every collector in it. otelcol-contrib receives it over OpAMP; Grafana Alloy pulls it over remotecfg. Standard upstream builds, no forked collector or proprietary agent.

Problem

Pushing a config change to hundreds of collectors at once is how a single bad receiver takes down ingestion across the estate.

LinkMesh

Roll a change out to one group first — a canary environment or a single region — watch health and effective-config convergence, then promote it to the rest. Every collector reports its EffectiveConfig and health back over OpAMP, so you see the change land before you widen it.

Problem

A collector’s running config quietly diverges from what you pushed — a local override, a manual SSH edit, a half-applied change. You find out when telemetry stops arriving.

LinkMesh

LinkMesh compares each collector’s reported EffectiveConfig hash against the config it was assigned and flags the mismatch. The collector timeline shows exactly when a node reported a hash that differs from the last server push, and when it re-converged.

Problem

You cannot manage what you cannot list. The fleet’s size, versions, and placement live in people’s heads and a stale spreadsheet.

LinkMesh

Every enrolled collector is inventoried automatically — status, agent version, last-seen, host, and the group and environment it belongs to. Organize the fleet into groups (production, staging, per-region, per-tenant) and scope user access per group.

Problem

Configuring collectors means SSH, a config file per host, and a restart you hope succeeds. It doesn’t scale, and it audits nothing.

LinkMesh

LinkMesh is an OpAMP control plane. otelcol-contrib connects with the standard opampsupervisor over a single outbound port-443 connection; Grafana Alloy pulls the same managed config over its native remotecfg endpoint. RemoteConfig, connection settings, and health all flow over the protocol — no inbound ports, no SSH.

Problem

"Who changed the sampling rule, when, and can we undo it?" should be a one-click answer, not a forensic exercise.

LinkMesh

Every route, pipeline, 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.

Problem

A team ships a collector that forwards raw logs — PII included — straight to a backend, bypassing every masking and sampling rule you agreed on.

LinkMesh

Attach global processors to a group so masking, filtering, and sampling apply to every collector in it, independent of the local pipeline. New collectors inherit the group’s policy the moment they enroll.

Problem

Security wants logs in Splunk, SRE wants metrics in Prometheus, finance wants slow queries in BigQuery — all from the same sources.

LinkMesh

Define routes by label, environment, or tenant; the same collector fans out to multiple destinations with a different processing chain per route. The topology view shows live throughput on every edge.