LinkMesh

OpenTelemetry-native · OpAMP-first · On-premises

Observability Data Collection Management

LinkMesh OBSERVABILITY DATA COLLECTION MANAGEMENT Telemetry sprawls. Cost explodes. LinkMesh is OpenTelemetry-native OpAMP-first On-premises GitOps-driven Per-collector billed PII-aware Open standards No lock-in Self-hosted No volume-based licensing· pay per collector, not per GB Collect Any source, any signal. OTLP (gRPC + HTTP) Syslog (RFC 3164 / 5424) Filelog, journald, Kafka Prometheus + host metrics Refine Cut noise before it costs you. Drop, sample, aggregate Rate-limit by service or tag OTTL transforms with previews Per-component throughput Protect Mask PII on the host. Cards, emails, phone numbers Custom regex / OTTL rules Runs client-side, before egress Stays inside your network Route Right data to the right backend. By label, env, tenant, service Fan-out to multiple backends Per-route processing chains GitOps audit-trail every change How it all connects One control plane orchestrating every Collector in your pipeline SOURCES BACKENDS Logs Metrics Traces Loki Prometheus Kafka MANAGEMENT LinkMesh Server OPAMP CONTROL PLANE OPENTELEMETRY Collectors

Centralized orchestration and configuration management for your OpenTelemetry Collectors — from one control plane. Collect, refine, protect, and route telemetry from any source to any destination, with predictable per-collector pricing.

Both tiers are first-class. Mix and match across your fleet — switch any time.

Two enrollment tiers

Choose the path that fits your fleet

Standards-tier respects teams who already standardized on otelcol-contrib or Grafana Alloy — no second binary on the host. Managed-tier gives you the full canvas, host metrics, and remote control if centralized fleet operations is the priority.

Capability Standards Vanilla OpAMP Managed LinkMesh agent + upstream Alloy
Install footprint ~10 lines of YAML .deb / .rpm package
Host CPU / memory Auto-collected
Remote control (restart, reload, exec) Restart / reload Full
Self-upgrades with rollback Your package manager Agent-managed
Service auto-detection on enrollment Detects services + suggests receivers
Log onboarding Author receiver YAML manually Guided picker + template library

First time? Walk through the full setup with screenshots on docs.linkmesh.io/quickstart.

Built for the platform team

LinkMesh is the control plane for your telemetry pipelines. Four principles shape every design decision.

Composable

Open standards (OpenTelemetry), no lock-in. Your data stays yours, on your infrastructure.

Predictable

Collector-based pricing — capacity you can plan. No bills exploding when telemetry volume grows.

Trustworthy

On-prem, PII-aware, audit-friendly. Sensitive fields can be masked before telemetry leaves the host.

Connected

Mesh sources to destinations through a single fabric. Route by labels, environments, tenants.

The pipeline narrative

Collect

Onboard logs, metrics, and traces from any source using standard OpenTelemetry Collectors.

Refine

Filter, enrich, sample, and reduce noisy telemetry before it reaches expensive backends.

Protect

Mask credit cards, emails, phone numbers, and arbitrary fields inside customer infrastructure.

Route

Send telemetry to the right destination based on labels, services, environments, or tenants.

For the technical model behind these capabilities — Collectors, Sources, Pipelines, Routes, Destinations — see Concepts on docs.linkmesh.io.

25 Collectors free for evaluation.

Test enrollment, pipeline configuration, PII masking, and multi-destination routing in your own environment — no volume-based cost risk during the trial. Pricing scales by managed Collector after that.