Hello,

The example in section 2.2. Using LQL in Python is not working
https://docs.checkmk.com/latest/en/livestatus.html#heading__using_lql_in_python

OMD[central]:~$ python3 live_example.py 
Traceback (most recent call last):
  File "/opt/omd/sites/central/live_example.py", line 17, in <module>
    sock.sendall("GET status\nOutputFormat: json\n")
TypeError: a bytes-like object is required, not 'str'

Would be nice if there would be a functional code snipped.

I have enabled SAML Auth using the documentation located here: https://docs.checkmk.com/latest/de/draft_saml.html

on 2 CheckMK Instances which are connected via Distributed Monitoring

This way if you login to each site separately, you are prompted for authentication via saml and MFA

I get the issue below as the sites cannot login to one another on their own auth channel

Do you have a way to Bypass SAML for Site to Site Communication?

In the docs for v2.1.0 the docker run example still uses 2.0.0-latest tag.

See:

• de: https://github.com/tribe29/checkmk-docs/blame/2.1.0/de/introduction_docker.asciidoc#L62
• en: https://github.com/tribe29/checkmk-docs/blame/2.1.0/en/introduction_docker.asciidoc#L60

Is 2.0.0-latest still the recommended version or did just somebody forgot to update the docs?

Can we get a book version of the docs as epub and pdf please ?

I would like to read all the docs on my ebook reader.
Like a book.

Since this is asciidoc(tor) this should be easy to implement, shouldn't it ?

Hi,

Idea here is to whatever the events are generated in checkMK it should forward those event notifications from CheckMK to Moogsoft AIOps webhook api which will then take care of creating the incidents in ServiceNow. I know this will be done via custom script but I am not aware of that script.

Can someone suggest how this can be implemented? Is there a prewritten custom script from CheckMK to forward the event notifications? I will be glad if someone have that script or can prepare it for me?

I've set up my checkmk Raw for HTTPS as described in the docs long before upgrading to version 2.1.0 Raw and everything worked as expected.

After the upgrade to version 2.1.0 Raw, I now have the issue, that I'm not able to register a host as described in the docs to use the newly enhanced agent.

The error that shows up is the following:

cmk-agent-ctl register -H <hostname> -s <servername> -i <sitename> -U <username> -v
INFO [cmk_agent_ctl] starting
ERROR [cmk_agent_ctl] Failed to discover agent receiver port from Checkmk REST API, both with http and https.

Error with http:
Failed to discover agent receiver port from http://<servername>/<sitename>/check_mk/api/1.0/domain-types/internal/actions/discover-receiver/invoke
error sending request for url (http://<servername>/<sitename>/check_mk/api/1.0/domain-types/internal/actions/discover-receiver/invoke): error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1914: (self signed certificate)
error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1914: (self signed certificate)
error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1914: (self signed certificate)
error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1914:

Error with https:
Failed to discover agent receiver port from https://<servername>/<sitename>/check_mk/api/1.0/domain-types/internal/actions/discover-receiver/invoke
error sending request for url (https://<servername>/<sitename>/check_mk/api/1.0/domain-types/internal/actions/discover-receiver/invoke): error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1914: (self signed certificate)
error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1914: (self signed certificate)
error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1914: (self signed certificate)
error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1914:

I also tried it with the flag --trust-cert, which also doesn't work.

The interesting part is, that it works from the monitoring-server itself, but not for any other hosts.

If I disable the HTTPS redirect condition in 000-default.conf and restart the apache2-service, I can also register other hosts and not only the monitoring server itself.
It also seems as it's not an SSL issue, since the attempt to register (with the disabled redirect) shows me the certificate of the monitoring server.

Could you please update this section, so HTTPS redirects are working and the use of the newly enhanced agent is also possible?
Thank you and best regards!

https://docs.checkmk.com/latest/en/monitoring_docker.html

Add clarification that plugin must me marked as executable, for example:

2. Setting up
   2.1. Installing the agent and plug-in
   To be able to monitor a Docker node with Checkmk, it must first be monitored with the normal Linux agent. This will give you a basic monitoring of the host system, however there will be no information about the Docker daemon or about the container.

You will need the mk_docker.py agent plug-in, which you can find here: Setup > Agents > Other operating systems > Plugins

Install the plug-in to /usr/lib/check_mk_agent/plugins. For information on installing an agent plug-in, see the Linux agent article.

mv mk_docker.py /usr/lib/check_mk_agent/plugins
chmod + x /usr/lib/check_mk_agent/plugins/mk_docker.py

https://docs.checkmk.com/latest/en/omd_basics.html#script_mode

The suggestion says

omd config show

When in reality it should follow the same as the other example and suggest to use omd config show mysite

After an upgrade from Ubunt 18.04 to 20.04 and from 20.04 to 22.04.
The Site user is removed from the omd group:
root@shvcmk:/etc # grep omd group
omd:x:130:

The site starts but the icmp will not start anymore. So this is really critical.
2023-08-17 14:03:24 [5] [rrdcached thread] [rrdcached at "/omd/sites/sh/tmp/run/rrdcached.sock"] successfully connected
2023-08-17 14:03:26 [4] [icmpreceiver 3130834] closed connection
2023-08-17 14:03:26 [3] [icmpreceiver 3130834] exited with status 1
2023-08-17 14:03:26 [5] [icmpreceiver 3130945] started, commandline: /omd/sites/sh/lib/cmc/icmpreceiver
2023-08-17 14:03:29 [4] [icmpreceiver 3130945] closed connection
2023-08-17 14:03:29 [3] [icmpreceiver 3130945] exited with status 1
2023-08-17 14:03:29 [5] [icmpreceiver 3131029] started, commandline: /omd/sites/sh/lib/cmc/icmpreceiver
2023-08-17 14:03:32 [4] [icmpreceiver 3131029] closed connection
2023-08-17 14:03:32 [3] [icmpreceiver 3131029] exited with status 1
2023-08-17 14:03:32 [5] [icmpreceiver 3131031] started, commandline: /omd/sites/sh/lib/cmc/icmpreceiver

Please Update the documentation to check /etc/group

Regards,
Peter Rupp

https://docs.checkmk.com/latest/en/monitoring_kubernetes.html

Support forKubernetes versions 1.18 and newer is currently limited, due to the fact that the official Kubernetes Python Client is not yet compatible with Kubernetes' newest API versions.

The python client supports Kubernetes ver. 1.21.x
https://github.com/kubernetes-client/python