Linux server
DEB/RPM or APT/YUM; Docker with a persistent /data volume.
Deployment guide →Plan a compatible installation
Check your runtime, deployment method and operational limits before the first rollout.
Collector versions and compatibility
Validated versions reported by the product documentation. This does not mean every newer release has been tested.
| Runtime | Minimum supported | Validated version | Configuration | Setup guide |
|---|---|---|---|---|
| otelcol-contrib | 0.151.0 | 0.153.0 | OpAMP + opampsupervisor | Connect collector |
| Grafana Alloy | 1.13.0 | 1.13.2 | remotecfg | Connect collector |
Reviewed on . Current support matrix in maintained documentation.
The documentation sets no upper version limit. Validate newer releases against your configuration before rollout. Below the minimum, missing components can cause the entire configuration to be rejected.
Documented deployment methods
Linux collectors
Upstream Alloy or otelcol-contrib with OpAMP Supervisor.
Deployment guide →Kubernetes collectors
Alloy via Helm; otelcol-contrib as a DaemonSet. This guide deploys the collector fleet.
Deployment guide →Windows collectors
Check platform-specific installation and component availability; the LinkMesh server runs on Linux.
Deployment guide →Known limitations
- Alloy uses remotecfg, not OpAMP. For otelcol-contrib, opampsupervisor applies remote configuration and restarts the collector when it changes.
- Local Alloy component labels must not collide with centrally managed components.
- The optional LinkMesh agent is version-coupled to the server. Check the maintained matrix for that pairing; collector runtime versions follow a separate policy.
- BoltDB supports one server instance. The documentation marks multi-instance HA with MongoDB as preview; plan production accordingly. Operational requirements