|Title||New builtin tag group "piggyback" allows to explictly turn piggyback data usage on/off|
|Checkmk Edition||Checkmk Raw Edition (CRE)|
|Compatibility||Compatible - no manual interaction needed|
Piggyback data is currently only read when the host has a Check_MK service. For some systems, the existance of the Check_MK service solely depends on the existance of piggyback files for the given host. During the config generation phase of the monitoring core, race conditions could apply, where a host might receive no Check_MK service.
This werk introduces an explicit piggyback host tag, which allows you to enforce/disable the use of piggyback data. Per default this option is currently set to Automatically detect piggyback usage, to be compatible with the previous behaviour.
You should explictly set the Use piggyback data option if you have a ping only host, which receives additional piggyback data from another host. This actively prevents beforementioned race conditions.