Our second Checkmk Feature Pack will be released this month! The feature pack consists of plugins to enhance your Checkmk installation and is optional. Your feedback is important to us, so we want to share the content of it with the community first.
The MKPs are available for download at the Checkmk Exchange and you can see all of them here . Please try them out and give any feedback you have.
Great to have these plugins back-ported to 1.6 and released as feature packs now. After seeing it at the conference Iāve tried the Prometheus integration in the 1.7 dev build, but couldnāt get it to work.
Now thatās itās released, does it come with any documentation on how to set it up? Because I canāt find any documentation on the subject in the official guide.
Would be good if the Cisco ASA plugin is not released in this version as it needs a little bit of revision.
Someone from the team should compare this with the other Cisco plugins available on the exchange.
It is also possible to contact me directly for some clarification.
thank you for looking at the Cisco ASA VPN monitoring stuff. Concerning the feature pack 2, we unfortunately do not have enough time any more to consider any merges, so for the fp2, the code for the Cisco VPN monitoring will stay as it is.
However, that being said, we would be happy to consider a merge in the future. For that, please create a pull request on our checkmk github. If you do so, please mention my name there and I will happily look into it.
I saw in the documentation for the Prometheus Integration, on the node exporter there should be also a section for network interfaces / traffic along to CPU, Disk and Filesystems by default in 1.7. I havenāt that in mind before, sorry.
Has anyone been able to work with the new prometheus plugin? Iāve installed it on version 1.6.0.p12 which came with prometheus-1.0.mkp, but on enabling kube-state-metrics a full scan fails with an error.
Starting job...
+ FETCHING DATA
[special_prometheus] Execute data source
[special_prometheus] ERROR: Agent exited with code 1: 'with_cpu_limits'
[piggyback] Execute data source
No piggyback files for 'prometheus-server.prometheus.svc.cluster.local'. Skip processing.
No piggyback files for '10.100.113.194'. Skip processing.
Completed.
I did an āmkp remove prometheusā and installed the latest version 1.1 from the exchange site, but the error persists.
I then updated check_mk to 1.6.0p13, no changes.
Weāre running prometheus v2.18.1.
If we donāt use kube-state-metrics and we use the node exporter or cAdvisor the scan works ok.
Provided info I can troubleshoot this more thoroughly.
Also, Iām not sure about this, but it seems the node-exporter is cycling in round robin fashion through all the kubernetes nodes when getting CPU and memory info.
The feature pack consists of plugins to enhance your Checkmk installation and is optional. Your feedback is important to us, so we want to share the content of it with the community first.
