At FOSDEM this year we met some great people and great projects, one of which was PatchMon! If you have never heard about PatchMon: this project is creating a dedicated solution to make needed security updates of Linux and FreeBSD servers visible.
After FOSDEM we connected again and @mschlenker drafted the first version of a community plugin to integrate PatchMon and Checkmk.
Now we are looking for testers! If you use Checkmk and PatchMon (or maybe you always considered adding it to your monitoring stack but never got to it?) check out the plugin here and let us know your feedback!
If you have any questions, we are also ready to answer them
Disclaimer: even though created by a team member, it is not an official Checkmk initiative but a community effort from @mschlenker and we will be happy to see other enthusiasts join it
I got a first statement, emphasizing, that AI can be helpful, but has to be “micro-managed” to be reliable. Points for AI being considered helpful are mostly GitHub workflow and failing tests:
We have had our issues in the past but our GitHub workflow processes when submitting goes through code quality, linting, formatting, building the docker images for frontend and backend, as well as the go agent going through all the tests too.
Regarding AI generated code contributions by third parties, they remain critical. Sometimes re-factoring user contributed code can be hard work:
We don’t blindly accept the Claude requests, there was one big PR by a community member who used Claude code pretty heavily in his commit in relation to server (CIS benchmarking and OIDC) but we refactored and went through it all again, mostly edited.
I guess, many of the devs within Checkmk would sign this:
AI isn’t at all a bad thing if done right and properly, but the proof is in the pudding as they say.
