Concepts

LinkMesh has a handful of first-class entities. Once you understand the vocabulary, the UI maps cleanly to what’s running on disk and what flows through the network.

• Collector — an upstream OTel runtime (Grafana Alloy or otelcol-contrib) running on a host you operate; the optional agent is a separate onboarding add-on, not the collector itself
• Collector Group — N collectors sharing one config, for redundancy or scale-out
• Source — an inbound receiver (syslog, OTLP, file tail, …), activated on a collector to start ingesting
• Pipeline — a reusable processing recipe: a chain of processors (filter, transform, mask, enrich)
• Route — the matcher that binds a source on a collector to a pipeline and to one or more destinations
• Destination — the terminal exporter (Loki, ClickHouse, S3, Kafka, OTLP, …)
• Enrollment tokens — short-lived single-use credentials a new host uses to bootstrap its mTLS identity

For the marketing-level pitch behind these entities — what problems they solve and why the model looks like this — see Features on linkmesh.io.