A self-hosted OpAMP server for your collector fleet

Problem

OpAMP is a protocol, not a product. To use it you need a server on the other end of the connection — one you can run yourself, not a hosted endpoint your agents phone home to.

LinkMesh

LinkMesh is an OpAMP server you self-host. otelcol-contrib connects with the standard opampsupervisor over a single outbound port-443 connection; the server manages the agent from there. No proprietary agent, no vendor cloud in the path.

Problem

Hand-editing a config file per host and restarting is how OpAMP’s whole reason for existing gets ignored. You want to push config from the server and have agents converge.

LinkMesh

LinkMesh renders configuration centrally and delivers it over OpAMP’s RemoteConfig message. Agents apply it and report back their EffectiveConfig and health, so the server always reflects what is actually running on each host.

Problem

RemoteConfig alone is half the loop. Without the agent reporting what it actually applied, you are pushing config into the dark.

LinkMesh

Every agent reports its EffectiveConfig hash and health status back over the connection. LinkMesh surfaces convergence, flags an agent whose reported hash diverges from what it was assigned, and shows the timeline of applies and drift.

Problem

One agent over OpAMP is a demo. Hundreds of agents, grouped by environment and rolled out to safely, is the actual job.

LinkMesh

Organize agents into groups, stage a config rollout to one group before promoting it, keep a live inventory of versions and status, and version every change in Git with one-click rollback — all over the same OpAMP connection.