[checkmk-commits] [tribe29/checkmk] 91d2ff: 12180 Display services of unimplemented check plugins

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: 91d2ff4562c1b317478e64cf72d4e9d00dcd407a https://github.com/tribe29/checkmk/commit/91d2ff4562c1b317478e64cf72d4e9d00… Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com> Date: 2021-02-26 (Fri, 26 Feb 2021) Changed paths: A .werks/12180 M cmk/base/automations/check_mk.py M cmk/base/check_table.py M cmk/base/checking/__init__.py M cmk/base/discovery/__init__.py M tests/unit/cmk/base/test_check_table.py Log Message: ----------- 12180 Display services of unimplemented check plugins Previously services with unimplemented check plugins have been filtered, and where (almost) never seen. They were reported as 'vanished' by the Checkmk Discovery check, but did *not* show on the discovery page, nor in the services page. They are now treated as regular services, with the service description "Unimplemented check <name>". They will always be in {{UNKNOWN}} state. This situation can occur for instance if you uninstall an MKP, or modify a plugin locally and make a mistake. If you suddenly encounter such services after an upgrade to Checkmk 2.0, it means that you had such services in your configuration all along. You can remove them from your configuration just as any other service. Change-Id: I6fe3cf71d4f390227207336ef6b8b22349d5a6f2 Commit: a407d20ec19119afb8a76eec56e9c1fadcf219cd https://github.com/tribe29/checkmk/commit/a407d20ec19119afb8a76eec56e9c1fad… Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com> Date: 2021-02-26 (Fri, 26 Feb 2021) Changed paths: M cmk/base/api/agent_based/register/export.py Log Message: ----------- agnet_based/register: fixes in doc Change-Id: Ib477756a1ab1d858e22779767a8baab2371f7e28 Compare: https://github.com/tribe29/checkmk/compare/c39fe7ec3b56...a407d20ec191