it seems that because of this issue: Rittal temperature check regression check_temperature has been updated in the last three days and it is now not possible to use the unique_name variable in the check_temperature function any more.
This fix also been pushed into the 2.3 branch for p7 but we are using the unique_name in some of our current check plugins, and the error leads to hundreds of crashing checks from devices where temperatures are present.
Isn´t that in incompatible change in a major version that should at least be documented or announced anywhere ?
For some context:
Strictly speaking, the code you are using is not part of the API, so we do not promise a stable interface here. However, we sympathize with your situation, and in this case we can go for a different solution that will not break your code. But beware: Maybe in the future we will (have to) make incompatible changes to that code.
It’s unfortunate: We currently can’t promise stability here, on the other hand we do believe it is desirable to have a consistent plugin landscape. Using these functions is one of the best ways to achieve that – with the severe downside you are currently experiencing.
I think this shows a need for yet another API that Checkmk should consider commiting to: Some check plugins that do offer a stable interface to tap into. For some types of checks (temperature, fans, diskspace and CPU utilization, for instance) it would be nice to have canonical plugins that can be easily used by creating appropriate section plugins (which was not possible pre “Check API” version 1). That would increase consistency a lot, and avoid this problem.
Alas – there’s so much to do…
.