Werk #17202: Distributed piggyback: Piggyback data for distributed setups
| Component | Checks & agents | ||
| Title | Distributed piggyback: Piggyback data for distributed setups | ||
| Date | Oct 21, 2024 | ||
| Level | Major Change | ||
| Class | New Feature | ||
| Compatibility | Compatible - no manual interaction needed | ||
| Checkmk versions & editions |
|
This feature allows the piggyback mechanism to be used across site borders.
In Checkmk versions prior to 2.4, the piggyback source and the piggybacked host always had to be monitored on the same site. It now suffices if they are part of the same distributed setup.
This is achieved by the introduction of the piggyback-hub:
A service that will send incoming piggyback data to whatever site the piggybacked host is monitored on.
The transmitted data will be sent via the newly introduced message broker. In most setups the messages will be routed via the central site, but direct ("peer-to-peer") connections can be configured in the Connections menu of the Distributed Monitoring Setup page. The data transport is secured via mTLS. In the Checkmk MSP Edition, this layer also ensures that communication between different customers is not possible.
The Piggyback Connector of the Dynamic Configration Daemon now also supports the creation of hosts on other sites.
This feature is disabled by default, and can be enabled on one or all sites via each sites omd config.
For proper DCD support it needs to be enabled on the central site, even if peer-to-peer connections are configured for the participating remote sites.