Hi,
We are trying to monitor Kubernetes in CheckMK using 1.5.0p13 Enterprise version.
Where do we specify the Kubernetes Cluster URL when configuring Monitoring?
We followed this document but don’t know how CheckMK would contact the Kubernetes cluster or vice-versa.
https://mathias-kettner.com/cms_monitoring_kubernetes.html
The document describes:
2.4. Adding a Kubernetes-Cluster to the Monitoring
The monitoring under Check_MK functions in two levels. The Kubernetes Cluster
itself is monitored as a host. For the individual Kubernetes nodes
we use the piggyback principle. That means each node is monitored
as a separate host in Check_MK. The monitoring data from
these hosts are not retrieved separately from Kubernetes, but instead
derived from the data from the Kubernetes cluster.
···
How do you monitor K8S Cluster as a host or how do you use the piggyback method?
Where is it outlined in the document how to do this?
Thank you
mukarram
Hi Mukarram,
the manual article about the "piggyback" mechanic is missing at the moment.
But in some words it means a host is delivering data for a other
monitoring object and check_mk assigns this data automatically to this
object.
I think the setup process for the agent is complete and working.
Now you create a host und assign the configured special agent to this host.
The kubernetes services should be visible inside service discovery.
Next step is to create the dummy hosts for nodes inside the kubernetes cluster.
Create a host object with the same name as your node has inside
kubernetes. It is possible to look for the correct writing inside
"~/tmp/check_mk/piggyback".
There you find a folder for every host object with piggyback data.
Best regards
Andreas
···
Am Di., 30. Apr. 2019 um 00:38 Uhr schrieb Mukarram Syed <mukarram.syed@8x8.com>:
Hi,
We are trying to monitor Kubernetes in CheckMK using 1.5.0p13 Enterprise version.
Where do we specify the Kubernetes Cluster URL when configuring Monitoring?
We followed this document but don't know how CheckMK would contact the Kubernetes cluster or vice-versa.
https://mathias-kettner.com/cms_monitoring_kubernetes.html
The document describes:
2.4. Adding a Kubernetes-Cluster to the Monitoring
The monitoring under Check_MK functions in two levels. The Kubernetes Cluster itself is monitored as a host. For the individual Kubernetes nodes we use the piggyback principle. That means each node is monitored as a separate host in Check_MK. The monitoring data from these hosts are not retrieved separately from Kubernetes, but instead derived from the data from the Kubernetes cluster.
How do you monitor K8S Cluster as a host or how do you use the piggyback method?
Where is it outlined in the document how to do this?
Thank you
# mukarram
_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
Manage your subscription or unsubscribe
https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en
I am testing this right now too. Documentation is lacking some pieces, like how to create the kubernetes cluster ‘host’. I am assuming it should be configured with ‘no ip’ since it is just a landing place for the cluster data.
I added the cluster url in the datasource program for Kubernetes. (custom URL prefix)
Also i’m receiving the certificate SSL error described here when I run the agent from the cli- https://mathias-kettner.com/cms_monitoring_kubernetes.html#Importing%20a%20certificate%20into%20Check_MK
···
On Thu, May 2, 2019 at 5:17 AM Andreas Döhler andreas.doehler@gmail.com wrote:
Hi Mukarram,
the manual article about the “piggyback” mechanic is missing at the moment.
But in some words it means a host is delivering data for a other
monitoring object and check_mk assigns this data automatically to this
object.
I think the setup process for the agent is complete and working.
Now you create a host und assign the configured special agent to this host.
The kubernetes services should be visible inside service discovery.
Next step is to create the dummy hosts for nodes inside the kubernetes cluster.
Create a host object with the same name as your node has inside
kubernetes. It is possible to look for the correct writing inside
“~/tmp/check_mk/piggyback”.
There you find a folder for every host object with piggyback data.
Best regards
Andreas
Am Di., 30. Apr. 2019 um 00:38 Uhr schrieb Mukarram Syed > > mukarram.syed@8x8.com:
Hi,
We are trying to monitor Kubernetes in CheckMK using 1.5.0p13 Enterprise version.
Where do we specify the Kubernetes Cluster URL when configuring Monitoring?
We followed this document but don’t know how CheckMK would contact the Kubernetes cluster or vice-versa.
https://mathias-kettner.com/cms_monitoring_kubernetes.html
The document describes:
2.4. Adding a Kubernetes-Cluster to the Monitoring
The monitoring under Check_MK functions in two levels. The Kubernetes Cluster itself is monitored as a host. For the individual Kubernetes nodes we use the piggyback principle. That means each node is monitored as a separate host in Check_MK. The monitoring data from these hosts are not retrieved separately from Kubernetes, but instead derived from the data from the Kubernetes cluster.
How do you monitor K8S Cluster as a host or how do you use the piggyback method?
Where is it outlined in the document how to do this?
Thank you
mukarram
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
Manage your subscription or unsubscribe
https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
Manage your subscription or unsubscribe
https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en