Checkmk now supports monitoring OpenShift clusters. The OpenShift monitoring builds on top of
Checkmk's existing Kubernetes monitoring. However, the metrics are collected via methods tailored to
OpenShift due to the incompatibility of the Checkmk collectors with OpenShift. This new
monitoring leverages the Kubernetes API and the off-the-shelf Prometheus monitoring stack of
OpenShift. Thus, no additional workload needs to be deployed in your OpenShift cluster. In
particular, the OpenShift monitoring does not require the Checkmk Cluster collector.
This feature can be enabled by configuring the rule Kubernetes.
Enabling the collectors has the following benefits.
- Allow monitoring CPU and Memory usage via the kube_memory and kube_cpu
- Enable machine level monitoring on each node.
- Populate the Kubernetes dashboard with data.
The following check plugins are part of machine-level monitoring of a node.
- mem_used (inventory plugin)
While Prometheus acts as a data source for the OpenShift monitoring, this does not imply that this
monitoring is compatible to any Prometheus stack. For compatibility Checkmk requires the identical
set-up of Prometheus as in OpenShift. This includes scraping the same collectors, renaming metrics
in the same manner, having the same recording rules and so forth. Thus, we highly recommend using
the Checkmk collectors for any non-OpenShift Kubernetes environment.
The Checkmk Openshift monitoring will display different metric values for some resources than reported
on the Openshift dashboard.
Zur Liste aller Werks