Checkmk werks level1 April 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
306 discussions

[2.4.0] Checkmk Werk 16667 created: discovery: fix writing of autochecks file for nodes

by Checkmk werks level 1

[//]: # (werk v2) # discovery: fix writing of autochecks file for nodes key | value ---------- | --- date | 2024-04-25T12:29:22+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes For clustered services the nodes' autocheck files would be written with the aggregated clustered service information. Now, at least for the autodiscovery, this is fixed and the individual node information is written.

4 months, 1 week

[2.3.0] Checkmk Werk 15842 created: Enhanced MS SQL Server monitoring

by Checkmk werks level 1

[//]: # (werk v2) # Enhanced MS SQL Server monitoring key | value ---------- | --- date | 2024-04-03T07:47:56+00:00 version | 2.3.0b4 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.

4 months, 1 week

[2.3.0] Checkmk Werk 15844 created: Microsoft SQL Server (Windows) ruleset is deprecated

by Checkmk werks level 1

[//]: # (werk v2) # Microsoft SQL Server (Windows) ruleset is deprecated key | value ---------- | --- date | 2024-04-17T13:40:06+00:00 version | 2.3.0b6 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.

4 months, 1 week

[2.4.0] Checkmk Werk 16794 created: "checkgroup_parameters:if": Rename to "checkgroup_parameters:interfaces"

by Checkmk werks level 1

[//]: # (werk v2) # "checkgroup_parameters:if": Rename to "checkgroup_parameters:interfaces" key | value ---------- | --- date | 2024-04-26T11:27:20+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | no This only affects you if you are configuring rules through the REST API. In order to make the "checkgroup_parameters:if" ruleset compliant with the new Ruleset API, it has been renamed to "checkgroup_parameters:interfaces". Any configuration inside Checkmk will be automatically updated, however any outside references to the old name will have to be adjusted manually.

4 months, 1 week

[2.2.0] Checkmk Werk 16698 created: mknotifyd: Log to correct file after logrotate

by Checkmk werks level 1

Title: mknotifyd: Log to correct file after logrotate Class: fix Compatible: compat Component: notifications Date: 1714032530 Edition: cee Level: 1 Version: 2.2.0p26 The logrotate cronjob rotated the logfile mknotifyd.log in the right way but the mknotifyd was not aware of the changed logfile, resulting in logging to the rotated file. The mknotifyd is now aware of a change of the logfile.

4 months, 2 weeks

[2.4.0] Checkmk Werk 16807 created: Ignore unknown "Disabled checks" during update config

by Checkmk werks level 1

[//]: # (werk v2) # Ignore unknown "Disabled checks" during update config key | value ---------- | --- date | 2024-04-24T12:25:30+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes If users had disabled checks that have since been removed or are temporarily unavailable (due to disabled MKPs for instance), they would be prompted with a message like ``` WARNING: Invalid rule configuration detected (Ruleset: ignored_checks, Title: Disabled checks, Folder: , -| Rule nr: 1, Exception: ifoperstatus is not an allowed value) ``` These invalid values are ignored now. They do no harm and they are dropped upon editing the rule.

4 months, 2 weeks

[2.4.0] Checkmk Werk 16425 created: APACHE_TCP_ADDR now allows IPv6 address

by Checkmk werks level 1

[//]: # (werk v2) # APACHE_TCP_ADDR now allows IPv6 address key | value ---------- | --- date | 2024-04-22T11:05:16+00:00 version | 2.4.0b1 class | fix edition | cre component | omd level | 1 compatible | yes Previously, using the command `omd config set APACHE_TCP_ADDR` with a IPv6 address would fail. For example, the command ``` $ omd config set APACHE_TCP_ADDR "[::]" ``` resulted in `Invalid value for '[::]'. Does not match allowed pattern.` With this Werk, it `omd` only checks that a `Listen` directive for Apache can be constructed from the `APACHE_TCP_ADDR`. In particular, this a IPv6 address can be configured. Such an address must be surrounded by square brackets.

4 months, 2 weeks

[2.4.0] Checkmk Werk 16681 created: check_http: Stricter address family configuration requirements

by Checkmk werks level 1

[//]: # (werk v2) # check_http: Stricter address family configuration requirements key | value ---------- | --- date | 2024-04-17T10:07:49+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | no The active check "http" allows different configurations for the address family in the host settings, among others the primary address family. If this option is selected, a primary IP address now has to be configured for the relevant host. An IP address also has to be configured for the host if no explicit address is configured in the rule. Note that this active check is being deprecated in favor of the newer "httpv2".

4 months, 2 weeks

[2.4.0] Checkmk Werk 16789 created: check_http: Improve handling of old service description

by Checkmk werks level 1

[//]: # (werk v2) # check_http: Improve handling of old service description key | value ---------- | --- date | 2024-04-18T16:02:21+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes If not configured otherwise, the service description of the active check "http" will be prepended with either "HTTP" or "HTTPS". In older installations only the "HTTP" prefix was possible and special handling was introduced to keep the old prefix for existing services. To improve the handling existing configurations of the "Service name" in the "Check HTTP service (deprecated)" rule may now be updated to contain the prefix "^HTTP" if the configured value does not start with a "^". This only changes the saved rule, the actual description of the service will not change.

4 months, 2 weeks

[2.4.0] Checkmk Werk 16698 created: mknotifyd: Log to correct file after logrotate

by Checkmk werks level 1

[//]: # (werk v2) # mknotifyd: Log to correct file after logrotate key | value ---------- | --- date | 2024-04-25T08:08:50+00:00 version | 2.4.0b1 class | fix edition | cee component | notifications level | 1 compatible | yes The logrotate cronjob rotated the logfile mknotifyd.log in the right way but the mknotifyd was not aware of the changed logfile, resulting in logging to the rotated file. The mknotifyd is now aware of a change of the logfile.

4 months, 2 weeks

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 April 2024