Connect your first collector.

Enroll your collectors

Connect with vanilla OpenTelemetry — no proprietary agent required.

LinkMesh manages supported upstream collector versions. Point otelcol-contrib at LinkMesh with the upstream opampsupervisor (OpAMP), or add a remotecfg block to Grafana Alloy. These are distinct remote-management protocols; both authenticate with a bearer token over port 443 and leave the data plane (OTLP) untouched. Use the enrollment token for OpAMP or the per-collector bearer token for Alloy. Follow the runtime-specific guide and verify the first connection.

otelcol-contrib · OpAMP

otelcol-contrib + opampsupervisor

The one-liner fetches both upstream binaries (collector + supervisor), writes the supervisor config, and starts the systemd unit. Swap in your own server's address if you're self-hosting.

curl -fsSL https://linkmesh.example.com/install-opamp.sh | \
  sudo sh -s -- --token YOUR_TOKEN

The supervisor opens a WebSocket to /v1/opamp, receives the config LinkMesh pushes, and writes it to the collector subprocess — you don't author the collector's config.yaml by hand. Full walkthrough: Onboard otelcol-contrib via OpAMP →

Grafana Alloy · remotecfg

Grafana Alloy

Alloy speaks its native remotecfg protocol — HTTP polling rather than OpAMP push. Add one block to your existing Alloy config, point it at the LinkMesh base URL, and authenticate with a per-collector bearer token minted from the collector detail page.

remotecfg {
  url            = "https://linkmesh.example.com"
  id             = constants.hostname
  poll_frequency = "60s"
  bearer_token   = env("LINKMESH_TOKEN")
}

Alloy reloads its pipelines automatically when the remote config changes — no service restart needed. Full walkthrough: Onboard Grafana Alloy via remotecfg →