Update 26-10-2019: This week, I received a message from Jan Leptien of Tribe29. Jan informed me that the company behind Check_MK, Mathias Kettner GmbH has re-branded itself and became Tribe29 GmbH. The why of that decision can be found here.
The product name switched from Check_MK to Checkmk, so please read “Checkmk” where you may encounter “Check_MK”. They also moved their website from from mathias-kettner.com to checkmk.com.
A good starting point for Checkmk is the official user Guide which can be found at: https://checkmk.com/cms.html
This post is the third part in a series about Check_MK and vSphere. In the second part, I showed you the options for monitoring an ESXi host without using vCenter Server. In this post we will explore the options for monitoring a vCenter Server on Windows and also the vCenter Server Appliance (VCSA).
vCenter Server Windows
For this POC we have a vCenter Server 6.0 U2 (build 3634793) on a Windows Server 2012 R2. As this is a normal Windows server, I installed the Check_MK agent for Windows and added the host to Check_MK. For the property Agent type, select “Check_MK Agent (Server)”.
By default the Check_MK Windows Agents presents – without further tweaking – a lot of information; CPU and Memory utilization, Disk I/O, status of the filesystems, status of the Network interfaces and many more.
Now it’s time to reveal the vSphere options. We follow the same procedure as we did for the ESXi host. In the WATO configuration go to Host & Service Parameters \ Datasource Programs and select Check state of VMware ESX via vSphere. Now create a second rule for the vCenter Server, start with providing a descriptive name.