Trigger distribution of changes on checks to all servers in a distributed environment

4 votes

When we make our own checks/plugins we sometimes need to change the sourcecode, when we do, we push the changes to a repository on an internal Gitlab server, the push then triggers a pipeline who in turn copies the new code on to the central server and sets the correct chown and chmod settings.

The pipeline works well, until it is time to get the code distributed to the other servers in the distributed environment.

As we are running the deployment in a pipeline on gitlab, theese files are updated but not showing in the CheckMK Web as changes that need to be activated.
The result is that the files stay on the central server, and are not distributed.

My suggestion is for you to build a way to somehow force “Activate changes” to all sites via commandline/rest api or possibly another way to initiate the distribution of such homemade checks.

Under consideration Site management Suggested by: Ronny Grønsdal Upvoted: 10 Apr, '25 Comments: 0

Comments: 0