Checkmk werks level2 July 2024

checkmk-werks-lvl2@lists.checkmk.com

1 participants
23 discussions

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

by Checkmk werks level 2

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.3.0b1 ------------------------------------<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.3.0b1 ? ^ ^ -

1 month, 1 week

[2.3.0] Checkmk Werk 16846 adapted: The custom instances of the MS SQL Server plugin are configured correctly

by Checkmk werks level 2

Werk 16846 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # The custom instances of the MS SQL Server plugin are configured correctly key | value ---------- | --- date | 2024-07-19T11:09:57+00:00 version | 2.3.0p12 class | fix edition | cee component | checks level | 2 compatible | yes Previously, configuring custom instances, WATO used wrong key names: `conn` instead of a correct `connection` and `auth` instead of a correct `authentication`. With this release the problem has been eliminated, If you are using custom instances you need to bake and deploy new agent package ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # The custom instances of the MS SQL Server plugin are configured correctly key | value ---------- | --- date | 2024-07-19T11:09:57+00:00 - version | 2.3.0p11 ? ^ + version | 2.3.0p12 ? ^ class | fix edition | cee component | checks level | 2 compatible | yes Previously, configuring custom instances, WATO used wrong key names: `conn` instead of a correct `connection` and `auth` instead of a correct `authentication`. With this release the problem has been eliminated, If you are using custom instances you need to bake and deploy new agent package

1 month, 2 weeks

[2.3.0] Checkmk Werk 16846 adapted: The custom instances of the MS SQL Server plugin are configured correctly

by Checkmk werks level 2

Werk 16846 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # The custom instances of the MS SQL Server plugin are configured correctly key | value ---------- | --- date | 2024-07-19T11:09:57+00:00 version | 2.3.0p11 class | fix edition | cee component | checks level | 2 compatible | yes Previously, configuring custom instances, WATO used wrong key names: `conn` instead of a correct `connection` and `auth` instead of a correct `authentication`. With this release the problem has been eliminated, If you are using custom instances you need to bake and deploy new agent package ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) - # WATO configures correctly custom imstances for MS SQL Server plugin + # The custom instances of the MS SQL Server plugin are configured correctly key | value ---------- | --- date | 2024-07-19T11:09:57+00:00 version | 2.3.0p11 class | fix edition | cee component | checks level | 2 compatible | yes - Previously, configuring custom instances, WATO used wrong names: + Previously, configuring custom instances, WATO used wrong key names: ? ++++ `conn` instead of a correct `connection` and `auth` instead of a correct `authentication`. With this release the problem has been eliminated, If you are using custom instances you need to bake and deploy new agent package

1 month, 2 weeks

[2.3.0] Checkmk Werk 16846 created: WATO configures correctly custom imstances for MS SQL Server plugin

by Checkmk werks level 2

[//]: # (werk v2) # WATO configures correctly custom imstances for MS SQL Server plugin key | value ---------- | --- date | 2024-07-19T11:09:57+00:00 version | 2.3.0p11 class | fix edition | cee component | checks level | 2 compatible | yes Previously, configuring custom instances, WATO used wrong names: `conn` instead of a correct `connection` and `auth` instead of a correct `authentication`. With this release the problem has been eliminated, If you are using custom instances you need to bake and deploy new agent package

1 month, 2 weeks

[2.4.0] Checkmk Werk 15842 adapted: Enhanced MS SQL Server monitoring

by Checkmk werks level 2

Werk 15842 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Enhanced MS SQL Server monitoring key | value ---------- | --- date | 2024-04-03T07:47:56+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 2 compatible | yes With this release MS SQL Server is monitored using new plugin and new GUI. The old plugin is still supported but are considered deprecated. Key Enhancements out-of-the-box: - Configuration flexibility: The plugin can be configured through a YAML config file for any edition and/or a graphical user interface (GUI) for enterprise edition or better. - Cross platform: The plugin can be deployed on Linux and Windows. - Enhanced monitoring capabilities: Supports monitoring of remote databases on both Linux and Windows hosts, in addition to local monitoring on Windows hosts. - Customizable monitoring sections: Sections are now selectable and configurable - Customizable SQL statements: you may change SQL statement either manually(place file in `mssql` sub directory in config dir) or using `Custom files` rule in GUI. - Multi-instance support: Enables the selection of different instances for monitoring. Every instance can be configured separately - Multi-host support: possible to monitor databases on various hosts using one deployed plugin. - Security enhancements: Limited support for certificates is now available. - Asynchronous operation: Any section with exception `instances` can be set up for asynchronous operation. - Piggyback: It's possible to direct the output of a plugin to a different host, rather than to the host that retrieves the data. - Other improvements: - Automatic detection of instances is possible for any Windows host, local and remote, depending on SQL Server Setup. - Full logging support including rotation and file limits - Limit for maximal connection counts - Cache time and timeout can be configured too With regard to the old plug-in, there are also a few restrictions at the moment: - The database instances must be accessible via TCP/IP. - If several databases are running on a system, each using their own IP addresses, these must be explicitly specified in the configuration of the agent plug-in, as the addresses and ports are currently not yet found automatically. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Enhanced MS SQL Server monitoring key | value ---------- | --- date | 2024-04-03T07:47:56+00:00 - version | 2.3.0b4 ? ^ ^ + version | 2.4.0b1 ? ^ ^ class | feature edition | cre component | checks level | 2 compatible | yes With this release MS SQL Server is monitored using new plugin and new GUI. The old plugin is still supported but are considered deprecated. Key Enhancements out-of-the-box: - Configuration flexibility: The plugin can be configured through a YAML config file for any edition and/or a graphical user interface (GUI) for enterprise edition or better. - Cross platform: The plugin can be deployed on Linux and Windows. - Enhanced monitoring capabilities: Supports monitoring of remote databases on both Linux and Windows hosts, in addition to local monitoring on Windows hosts. - Customizable monitoring sections: Sections are now selectable and configurable - Customizable SQL statements: you may change SQL statement either manually(place file in `mssql` sub directory in config dir) or using `Custom files` rule in GUI. - Multi-instance support: Enables the selection of different instances for monitoring. Every instance can be configured separately - Multi-host support: possible to monitor databases on various hosts using one deployed plugin. - Security enhancements: Limited support for certificates is now available. - Asynchronous operation: Any section with exception `instances` can be set up for asynchronous operation. - Piggyback: It's possible to direct the output of a plugin to a different host, rather than to the host that retrieves the data. - Other improvements: - Automatic detection of instances is possible for any Windows host, local and remote, depending on SQL Server Setup. - Full logging support including rotation and file limits - Limit for maximal connection counts - Cache time and timeout can be configured too With regard to the old plug-in, there are also a few restrictions at the moment: - The database instances must be accessible via TCP/IP. - If several databases are running on a system, each using their own IP addresses, these must be explicitly specified in the configuration of the agent plug-in, as the addresses and ports are currently not yet found automatically.

1 month, 3 weeks

[2.4.0] Checkmk Werk 16342 adapted: Rename service labels for Robotmk

by Checkmk werks level 2

Werk 16342 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Rename service labels for Robotmk key | value ---------- | --- date | 2024-03-25T12:28:56+00:00 version | 2.4.0b1 class | feature edition | cee component | multisite level | 2 compatible | yes This is a follow-up for werk #13872. The service labels have been renamed to 'cmk/rmk/html_last_log:yes' and 'cmk/rmk/html_last_error_log:yes'. The icons for the last log file and last error log file will have an icon based on the new labels as well as the old ones from werk #13872. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Rename service labels for Robotmk key | value ---------- | --- date | 2024-03-25T12:28:56+00:00 - version | 2.3.0b4 ? ^ ^ + version | 2.4.0b1 ? ^ ^ class | feature edition | cee component | multisite level | 2 compatible | yes This is a follow-up for werk #13872. The service labels have been renamed to 'cmk/rmk/html_last_log:yes' and 'cmk/rmk/html_last_error_log:yes'. The icons for the last log file and last error log file will have an icon based on the new labels as well as the old ones from werk #13872.

1 month, 3 weeks

[2.4.0] Checkmk Werk 15844 adapted: Microsoft SQL Server (Windows) ruleset is deprecated

by Checkmk werks level 2

Werk 15844 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Microsoft SQL Server (Windows) ruleset is deprecated key | value ---------- | --- date | 2024-04-17T13:40:06+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 2 compatible | no We've introduced a new `Microsoft SQL Server (Linux, Windows)` plug-in for MS SQL database monitoring, see [werk 15842: Enhanced MS SQL Server monitoring](https://checkmk.com/werk/15842). The new plugin extends the functionality of `Microsoft SQL Server (Windows)` by adding more options and features. We recommend that you upgrade to the `Microsoft SQL Server (Linux, Windows)` plug-in to monitor MS SQL databases. This new agent plugin can be deployed alongside the Checkmk agent on your database systems, just like the previous plugin. You can also use this plugin on any Windows or Linux server to monitor remote MSSQL servers over the network. The previous `Microsoft SQL Server (Windows)` rule set is deprecated and renamed to `Microsoft SQL Server (deprecated)`. Please note that you may need to adjust settings on your databases or continue running the old plug-in for the time being, as the agent plug-in cannot connect to local database instances that are not available over a TCP/IP connection. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Microsoft SQL Server (Windows) ruleset is deprecated key | value ---------- | --- date | 2024-04-17T13:40:06+00:00 - version | 2.3.0b6 ? ^ ^ + version | 2.4.0b1 ? ^ ^ class | feature edition | cre component | checks level | 2 compatible | no We've introduced a new `Microsoft SQL Server (Linux, Windows)` plug-in for MS SQL database monitoring, see [werk 15842: Enhanced MS SQL Server monitoring](https://checkmk.com/werk/15842). The new plugin extends the functionality of `Microsoft SQL Server (Windows)` by adding more options and features. We recommend that you upgrade to the `Microsoft SQL Server (Linux, Windows)` plug-in to monitor MS SQL databases. This new agent plugin can be deployed alongside the Checkmk agent on your database systems, just like the previous plugin. You can also use this plugin on any Windows or Linux server to monitor remote MSSQL servers over the network. The previous `Microsoft SQL Server (Windows)` rule set is deprecated and renamed to `Microsoft SQL Server (deprecated)`. Please note that you may need to adjust settings on your databases or continue running the old plug-in for the time being, as the agent plug-in cannot connect to local database instances that are not available over a TCP/IP connection.

1 month, 3 weeks

[2.2.0] Checkmk Werk 16437 adapted: omd: Improve Runtime with Many Sites

by Checkmk werks level 2

Werk 16437 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: omd: Improve Runtime with Many Sites Class: fix Compatible: compat Component: omd Date: 1720082692 Edition: cre Level: 2 Version: 2.2.0p32 With this Werk, all invocations of the <tt>omd</tt> command line tool are faster. This Werk should not affect behaviour in any other way. The performance improvements mostly affect hosts, which have a high number of sites. ------------------------------------<diff>------------------------------------------- Title: omd: Improve Runtime with Many Sites Class: fix Compatible: compat Component: omd Date: 1720082692 Edition: cre Level: 2 - Version: 2.2.0p31 ? ^ + Version: 2.2.0p32 ? ^ With this Werk, all invocations of the <tt>omd</tt> command line tool are faster. This Werk should not affect behaviour in any other way. The performance improvements mostly affect hosts, which have a high number of sites.

1 month, 3 weeks

[2.3.0] Checkmk Werk 16437 adapted: omd: Improve Runtime with Many Sites

by Checkmk werks level 2

Werk 16437 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # omd: Improve Runtime with Many Sites key | value ---------- | --- compatible | yes version | 2.3.0p11 date | 2024-07-04T08:44:52+00:00 level | 2 class | fix component | omd edition | cre With this Werk, all invocations of the <tt>omd</tt> command line tool are faster. This Werk should not affect behaviour in any other way. The performance improvements mostly affect hosts, which have a high number of sites. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # omd: Improve Runtime with Many Sites key | value ---------- | --- compatible | yes - version | 2.3.0p10 ? ^ + version | 2.3.0p11 ? ^ date | 2024-07-04T08:44:52+00:00 level | 2 class | fix component | omd edition | cre With this Werk, all invocations of the <tt>omd</tt> command line tool are faster. This Werk should not affect behaviour in any other way. The performance improvements mostly affect hosts, which have a high number of sites.

1 month, 3 weeks

[2.4.0] Checkmk Werk 16563 created: Ensure background jobs finish properly on stopping sites

by Checkmk werks level 2

[//]: # (werk v2) # Ensure background jobs finish properly on stopping sites key | value ---------- | --- date | 2024-07-09T14:38:01+00:00 version | 2.4.0b1 class | fix edition | cre component | core level | 2 compatible | yes Previously running background jobs were not properly cleaned up by `omd stop`. Those processes were terminated at the end of `omd stop` command which would clean up the processes in most cases, but lead to failed jobs and leave crash reports behind. Secondly a few background jobs depend on Redis. In case Redis is stopped while the jobs are still running, the jobs would fail and also leave a crash report behind. This change aims to solve both issues, by extending what happens during `omd stop`. The procedure roughly works like this: 1. First the apache process and site cron are stopped to prevent the start of new background jobs. This is done by the already existing logic. 2. The new init script `background-jobs` gives the jobs some time to finish. Ideally all jobs are stopped after 20 seconds. 3. The stop command does not have to forcefully kill the jobs anymore in this case. 4. As a last resort `omd stop` will terminate the still running jobs as before.

1 month, 4 weeks

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level2 July 2024