Each Linux VM hosts its own OMD site which all link together using the CheckMK Livestatus distributed deployment.
I have installed the CheckMK Exchange package onto the Central Server, which we currently use to make changes/view CheckMK as far as my knowledge thats the correct way?
Now that it is installed and enabled, how do I start making use of this package?
this is a fine example that we need more guidance for the user after installing an extension.
Raw edition users need to know that they can list the contents of the extension package with mkp files and then deduct from there that the extension brings an agent plugin that needs to be deployed on the monitored host.
Enterprise edition users should see similar information on the extension management page, maybe with pointers to the bakery ruleset.
Guess what I am doing today… (because of Tanzverbot)
I am in this whole extension documentation thing, many things to do documentation wise. We might rip the MKP article in two to have one for monitoring admins and one for extension developers to make sure such information does not get lost.
Very good point, thank you for pointing it out @r.sander !
I added it to our UX opportunities - not having enough guidance how to proceed within a workflow is kind of a red thread in Checkmk Can’t make any promises regarding timeline, but we keep it in mind!
@cameronmuirhead I hope the docs article helped you and you could now proceed
Yeah thanks all, managed to SSL monitoring working on a Windows machine following the guidance from above. Had to manually install the powershell script that comes as part of the package on one of our servers then rescan the host on CheckMK.
Going to attempt Linux today for the rest of our estate.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.
Can’t make any promises regarding timeline, but we keep it in mind!