Checkmk werks level1 November 2023

checkmk-werks-lvl1@lists.checkmk.com

1 participants
219 discussions

[2.1.0] Checkmk Werk 15714 adapted: Add support for Checkmk Appliance 1.7+

by Checkmk werks level 1

Werk 15714 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Add support for Checkmk Appliance 1.7+ Class: feature Compatible: compat Component: distros Date: 1701285077 Edition: cre Level: 2 Version: 2.1.0p37 ------------------------------------<diff>------------------------------------------- Title: Add support for Checkmk Appliance 1.7+ Class: feature Compatible: compat Component: distros Date: 1701285077 Edition: cre Level: 2 - Version: 2.2.0p17 ? ^ ^ + Version: 2.1.0p37 ? ^ ^

1 year

[2.2.0] Checkmk Werk 15714 created: Add support for Checkmk Appliance 1.7+

by Checkmk werks level 1

Title: Add support for Checkmk Appliance 1.7+ Class: feature Compatible: compat Component: distros Date: 1701285077 Edition: cre Level: 2 Version: 2.2.0p17

1 year

[2.1.0] Checkmk Werk 16263 created: Broken discovery result if services contained pipe symbol

by Checkmk werks level 1

Title: Broken discovery result if services contained pipe symbol Class: fix Compatible: compat Component: checks Date: 1701253848 Edition: cre Level: 1 Version: 2.1.0p37 If a services item contained the pipe symbol ("<tt>|</tt>"), the discovery check produced invalid metrics. This resulted in a rapidly growing <tt>var/log/web.log</tt>.

1 year

[2.2.0] Checkmk Werk 15714 created: Add support for Checkmk Appliance 1.7+

by Checkmk werks level 1

Title: Add support for Checkmk Appliance 1.7+ Class: feature Compatible: compat Component: distros Date: 1701285077 Edition: cre Level: 2 Version: 2.2.0p17

1 year

[2.3.0] Checkmk Werk 16264 created: Logwatch EC: Mergetype of forwarding rule is more consistent

by Checkmk werks level 1

Title: Logwatch EC: Mergetype of forwarding rule is more consistent Class: fix Compatible: compat Component: checks Date: 1701294709 Edition: cre Level: 1 Version: 2.3.0b1 The ruleset <i>"Logwatch Event Console Forwarding"</i> is more consistent now. The rules usually are merged, unless one of the rules configured "No forwarding", in which case the first such rule is applied. This is fixed now, this setting is now over-ridable as all the other settings. Existing rules are migrated automatically, the behaviour of existing rule combinations will not change.

1 year

[2.3.0] Checkmk Werk 16295 created: postfix_mailq_status: Rework discovery

by Checkmk werks level 1

Title: postfix_mailq_status: Rework discovery Class: fix Compatible: incomp Component: checks Date: 1700560692 Edition: cre Level: 1 Version: 2.3.0b1 With this werk the postfix status service is not discovered if Postfix is not running. The default mail queue is now discovered as "Postfix Status default". In order to make the check plugin work you have to perform a re-discovery on the affected hosts. Otherwise, the service "Postfix Status" (dicovered before this change) will stop working.

1 year

[2.3.0] Checkmk Werk 16301 created: fjdarye_pools: Discover on additional systems

by Checkmk werks level 1

Title: fjdarye_pools: Discover on additional systems Class: feature Compatible: compat Component: checks Date: 1701265703 Edition: cre Level: 1 Version: 2.3.0b1 As of this werk, the services "Thin Provisioning Pool ..." are discovered on additional Fujitsu storage systems, such as ETERNUS AF250 S3.

1 year

[2.3.0] Checkmk Werk 16263 created: Broken discovery result if services contained pipe symbol

by Checkmk werks level 1

Title: Broken discovery result if services contained pipe symbol Class: fix Compatible: compat Component: checks Date: 1701253848 Edition: cre Level: 1 Version: 2.3.0b1 If a services item contained the pipe symbol ("<tt>|</tt>"), the discovery check produced invalid metrics. This resulted in a rapidly growing <tt>var/log/web.log</tt>.

1 year

[2.1.0] Checkmk Werk 11440 adapted: WATO Cluster Discovery: Fixed bug showing services of NodeA on NodeB

by Checkmk werks level 1

Werk 11440 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: WATO Cluster Discovery: Fixed bug showing services of NodeA on NodeB Class: fix Compatible: incomp Component: wato Date: 1607006216 Edition: cre Knowledge: doc Level: 1 Version: 2.1.0b1 A WATO service discovery on a cluster host did incorrectly assign clustered services from NodeA to NodeB and vice versa. This was more of a GUI-related error, as it did not affect the computation of the core configuration. Affected users might have to trigger a rediscovery (tabula rasa). ------------------------------------<diff>------------------------------------------- Title: WATO Cluster Discovery: Fixed bug showing services of NodeA on NodeB Class: fix - Compatible: compat ? -- + Compatible: incomp ? ++ Component: wato Date: 1607006216 Edition: cre Knowledge: doc Level: 1 Version: 2.1.0b1 A WATO service discovery on a cluster host did incorrectly assign clustered services from NodeA to NodeB and vice versa. This was more of a GUI-related error, as it did not affect the computation of the core configuration. + Affected users might have to trigger a rediscovery (tabula rasa). + +

1 year

[2.2.0] Checkmk Werk 16279 created: service_discovery: redirect response header incorrectly configured to an absolute URI

by Checkmk werks level 1

Title: service_discovery: redirect response header incorrectly configured to an absolute URI Class: fix Compatible: compat Component: rest-api Date: 1700141008 Edition: cre Level: 1 Version: 2.2.0p16 When calling the service discovery endpoint, the redirect response header 'location' was set to an absolute URI, when it should be a relative URI. This werk addresses this issue by setting the URI correctly in the redirect responses.

1 year

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 November 2023