Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
16006 discussions

Checkmk Werk 8857: Docker container: Add hook functions to docker entrypoint

by Lars Michelsen

ID: 8857 Title: Docker container: Add hook functions to docker entrypoint Component: Linux Distributions Level: 1 Class: New feature Version: 1.7.0i1 With this change it is possible to to execute custom hook scripts during the container startup. This is useful in case you want to integrate your own logic into containers based on the Checkmk images. These hooks have been created: pre-create - post-create pre-start post-start To use them you need to At these steps, all scripts within docker-entrypoint.d/hook-name are executed. root@7ac2dc47037e:/# tree docker-entrypoint.d/ docker-entrypoint.d/ |-- post-create | |-- 01_foo.sh | |-- 02_bar.sh | `-- 03_baz.sh |-- post-start | |-- 01_foo.sh | |-- 02_bar.sh | `-- 03_baz.sh |-- pre-create | |-- 01_foo.sh | |-- 02_bar.sh | `-- 03_baz.sh `-- pre-start |-- 01_foo.sh |-- 02_bar.sh `-- 03_baz.sh

5 years, 2 months

Checkmk Werk 8848: Fix broken service discovery on remote sites (1.6.0b4 regression)

by Lars Michelsen

ID: 8848 Title: Fix broken service discovery on remote sites (1.6.0b4 regression) Component: WATO Level: 1 Class: Bug fix Version: 1.7.0i1

5 years, 2 months

Checkmk Werk 8847: Service discovery: Print warning instead of failing on discovery errors

by Lars Michelsen

ID: 8847 Title: Service discovery: Print warning instead of failing on discovery errors Component: WATO Level: 1 Class: Bug fix Version: 1.7.0i1 The service discovery page of WATO was terminating the service discovery on the first error, independent of which discovery function raised the error. In this situation a single broken check could break the service discovery functionality of WATO. On the command line (cmk -I) the default behavious is to proceed with the other discovery function when a single discovery function fails. This is now the default behavior of the WATO discovery page.

5 years, 2 months

Checkmk Werk 8846: Extension packages: Sort package list by name

by Lars Michelsen

ID: 8846 Title: Extension packages: Sort package list by name Component: WATO Level: 1 Class: Bug fix Version: 1.7.0i1

5 years, 2 months

Checkmk Werk 8845: Web-API: Prevent adding wrong encoded labels to hosts / rulesets

by Lars Michelsen

ID: 8845 Title: Web-API: Prevent adding wrong encoded labels to hosts / rulesets Component: WATO Level: 1 Class: Bug fix Version: 1.7.0i1 In previous 1.6 releases the Web API did not validate the labels that could e.g. be added to hosts strictly enough. When using "python" as "request_format" this could result in a broken configuration, leading to exceptions in several places of the GUI. The Web API now ensures the received labes are all unicode strings as Checkmk expects.

5 years, 2 months

Checkmk Werk 7719: Windows Agent 1.6: The section 'ps' by default doesn't generate full paths in the output

by Sergey Kipnis

ID: 7719 Title: Windows Agent 1.6: The section 'ps' by default doesn't generate full paths in the output Component: Checks & agents Level: 1 Class: Bug fix Version: 1.6.0b5

5 years, 2 months

Checkmk Werk 7718: Command line parameter version added to the Windows Agent

by Sergey Kipnis

ID: 7718 Title: Command line parameter version added to the Windows Agent Component: Checks & agents Level: 1 Class: New feature Version: 1.6.0b5

5 years, 2 months

Checkmk Werk 8842: Show host labels in "cmk -D HOST" output

by Lars Michelsen

ID: 8842 Title: Show host labels in "cmk -D HOST" output Component: Core & setup Level: 1 Class: New feature Version: 1.6.0b5 The effective host labels can now be displayed on the command line using "cmk -D HOST".

5 years, 2 months

Checkmk Werk 8840: Docker: Introduce host labels for different docker hosts

by Lars Michelsen

ID: 8840 Title: Docker: Introduce host labels for different docker hosts Component: Core & setup Level: 1 Class: New feature Version: 1.6.0b5 Docker nodes will now automatically marked with the discovered label "cmk_docker_object:node". The docker container host objects will be marked with the host label "cmk_docker_object:container".

5 years, 2 months

Checkmk Werk 8841: Change internal mechanic of discovered host labels

by Lars Michelsen

ID: 8841 Title: Change internal mechanic of discovered host labels Component: Core & setup Level: 1 Class: New feature Version: 1.6.0b5 The discovered host labels which were introduced during the first beta versions of Checkmk 1.6 had to be reworked for some reasons. The new implementation is now based on the Service discovery mechanism, which makes several things a lot easier for us. Host labels are now discovered during the procedure of Checkmk service discovery. All discovery functions of the checks are able to either discover services and host labels. <ul> <li>The "Check_MK Discovery" service tells you about new found host labels, just like about services.</li> <li>You can use the "Service discovery" page of WATO to view the discovered host labels. New discovered host labels now trigger a warning state by default. This state can be configured using the "Periodic service discovery" ruleset. <li>The automatic activation function, that can be configured in the "Periodic service discovery" ruleset may be used to automatically add new host labels on a regular base.</li> <li>Whenever you execute a service discovery (via command line, GUI or API), the host labels will also be discovered.</li> <li>CEE: The DCD can immediately add host labels when you have enabled the service discovery for a DCD connection.</li> </ul> Check programmers: You may add something like this to your discovery functions for creating host labels: C+: yield HostLabels( HostLabel(u"os", u"Windows"), HostLabel(u"type", u"security"), ) C-: This adds two host labels os:Windows and type:security to the host.

5 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1