Checkmk werks level1 May 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
549 discussions

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

by Checkmk werks level 1

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.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. ------------------------------------<diff>------------------------------------------- [//]: # (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.

5 months, 2 weeks

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

by Checkmk werks level 1

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.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. ------------------------------------<diff>------------------------------------------- [//]: # (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 plugin `Check MS SQL Server (Linux, Windows)` for MS SQL ? ^^^^ ------ ^^^^ + 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. The new + database monitoring, see + [werk 15842: Enhanced MS SQL Server monitoring](https://checkmk.com/werk/15842). - plugin extends the functionality of the `Microsoft SQL Server (Windows)` adding ? ---- ------- + The new plugin extends the functionality of `Microsoft SQL Server (Windows)` ? ++++++++ - more options and features. + 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 - We recommend upgrading to the `Check MS SQL Server (Linux, Windows)` plugin - for monitoring MS SQL databases. This new agent plugin can be deployed alongside the Checkmk agent on your database systems, just like the previous - plugin. Alternatively, you can deploy this plugin on any Windows or Linux ? ^^^^^^^^^^^^^^^^ ^ ---- + 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. - The previous rule `Microsoft SQL Server (Windows)` is deprecated and isn't - applied anymore. -

5 months, 2 weeks

[2.3.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.3.0b7 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.

5 months, 2 weeks

[2.3.0] Checkmk Werk 14229 adapted: Valuespecs: Fixed confusion of values when ListOf contains another ListOf and all have the same magic

by Checkmk werks level 1

Werk 14229 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Valuespecs: Fixed confusion of values when ListOf contains another ListOf and all have the same magic key | value ---------- | --- date | 2024-04-10T09:56:58+00:00 version | 2.3.0 class | fix edition | cre component | wato level | 1 compatible | yes Normally, ListOf elements embedded in other ListOf elements should contain a different magic value, otherwise errors will occur when processing forms. This werk here allows the use of identical magic values. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Valuespecs: Fixed confusion of values when ListOf contains another ListOf and all have the same magic key | value ---------- | --- date | 2024-04-10T09:56:58+00:00 - version | 2.3.0b7 ? -- + version | 2.3.0 class | fix edition | cre component | wato level | 1 compatible | yes Normally, ListOf elements embedded in other ListOf elements should contain a different magic value, otherwise errors will occur when processing forms. This werk here allows the use of identical magic values.

5 months, 2 weeks

[2.3.0] Checkmk Werk 16181 adapted: apc_powerswitch: upgrade old discovery parameters

by Checkmk werks level 1

Werk 16181 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # apc_powerswitch: upgrade old discovery parameters key | value ---------- | --- date | 2024-04-24T13:48:13+00:00 version | 2.3.0 class | fix edition | cre component | checks level | 1 compatible | yes Old apc_powerswitch discovery parameters are upgraded to the new format during `omd update`. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # apc_powerswitch: upgrade old discovery parameters key | value ---------- | --- date | 2024-04-24T13:48:13+00:00 - version | 2.3.0b7 ? -- + version | 2.3.0 class | fix edition | cre component | checks level | 1 compatible | yes Old apc_powerswitch discovery parameters are upgraded to the new format during `omd update`.

5 months, 2 weeks

[2.3.0] Checkmk Werk 16697 adapted: Ignore empty "Multiple sites" filter if "Site" filter is set

by Checkmk werks level 1

Werk 16697 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Ignore empty "Multiple sites" filter if "Site" filter is set key | value ---------- | --- compatible | yes version | 2.3.0 date | 2024-04-23T06:07:04+00:00 level | 1 class | fix component | multisite edition | cre If both filters "Multiple sites" and "Sites" were set, the "Multiple sites" filter was used, even if empty. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Ignore empty "Multiple sites" filter if "Site" filter is set key | value ---------- | --- compatible | yes - version | 2.3.0b7 ? -- + version | 2.3.0 date | 2024-04-23T06:07:04+00:00 level | 1 class | fix component | multisite edition | cre If both filters "Multiple sites" and "Sites" were set, the "Multiple sites" filter was used, even if empty.

5 months, 2 weeks

[2.3.0] Checkmk Werk 16803 adapted: Custom graphs: Fix crash in case of missing host/service/metric

by Checkmk werks level 1

Werk 16803 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Custom graphs: Fix crash in case of missing host/service/metric key | value ---------- | --- date | 2024-04-24T14:21:32+00:00 version | 2.3.0 class | fix edition | cee component | metrics level | 1 compatible | yes Custom graphs can contain elements whose host or service is non-existant. This happens for example when a host is removed from the monitoring after one of its metrics has been added to a custom graph. In such cases, no graph was rendered. Instead, the Checkmk UI displayed the message "Cannot calculate graph recipes" and showed a traceback. As of this werk, the UI instead renders no lines for such elements and denotes them with "n/a" in the graph legend. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Custom graphs: Fix crash in case of missing host/service/metric key | value ---------- | --- date | 2024-04-24T14:21:32+00:00 - version | 2.3.0b7 ? -- + version | 2.3.0 class | fix edition | cee component | metrics level | 1 compatible | yes Custom graphs can contain elements whose host or service is non-existant. This happens for example when a host is removed from the monitoring after one of its metrics has been added to a custom graph. In such cases, no graph was rendered. Instead, the Checkmk UI displayed the message "Cannot calculate graph recipes" and showed a traceback. As of this werk, the UI instead renders no lines for such elements and denotes them with "n/a" in the graph legend.

5 months, 2 weeks

[2.3.0] Checkmk Werk 16801 adapted: Custom graphs: Fix crash in case of unavailable scalars

by Checkmk werks level 1

Werk 16801 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Custom graphs: Fix crash in case of unavailable scalars key | value ---------- | --- date | 2024-04-23T10:22:44+00:00 version | 2.3.0 class | fix edition | cee component | metrics level | 1 compatible | yes When adding a scalar to a custom graph, it is possible that no value is available for this scalar. For example, this is the case when adding the CRIT threshold of a metric for which no thresholds are configured. In such cases, no graph was rendered. Instead, the Checkmk UI displayed the message "Cannot calculate graph recipes" and showed a traceback. This werk restores the correct behavior: No lines are rendered for unavailable scalars and they are denoted with "n/a" in the graph legend. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Custom graphs: Fix crash in case of unavailable scalars key | value ---------- | --- date | 2024-04-23T10:22:44+00:00 - version | 2.3.0b7 ? -- + version | 2.3.0 class | fix edition | cee component | metrics level | 1 compatible | yes When adding a scalar to a custom graph, it is possible that no value is available for this scalar. For example, this is the case when adding the CRIT threshold of a metric for which no thresholds are configured. In such cases, no graph was rendered. Instead, the Checkmk UI displayed the message "Cannot calculate graph recipes" and showed a traceback. This werk restores the correct behavior: No lines are rendered for unavailable scalars and they are denoted with "n/a" in the graph legend.

5 months, 2 weeks

[2.3.0] Checkmk Werk 16808 adapted: agent_threepar: The agent mistakenly only accepted default values as valid ones

by Checkmk werks level 1

Werk 16808 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # agent_threepar: The agent mistakenly only accepted default values as valid ones key | value ---------- | --- date | 2024-04-24T14:01:07+00:00 version | 2.3.0 class | fix edition | cre component | checks level | 1 compatible | yes This fixes a regression in Checkmk 2.3 beta. The integration to monitor "3PAR Configuration" mistakenly only accepted any subset of the default values as valid values. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # agent_threepar: The agent mistakenly only accepted default values as valid ones key | value ---------- | --- date | 2024-04-24T14:01:07+00:00 - version | 2.3.0b7 ? -- + version | 2.3.0 class | fix edition | cre component | checks level | 1 compatible | yes This fixes a regression in Checkmk 2.3 beta. The integration to monitor "3PAR Configuration" mistakenly only accepted any subset of the default values as valid values.

5 months, 2 weeks

[2.3.0] Checkmk Werk 16805 adapted: mkp-tool: CLIs 'package' command

by Checkmk werks level 1

Werk 16805 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # mkp-tool: CLIs 'package' command key | value ---------- | --- date | 2024-04-23T11:57:59+00:00 version | 2.3.0 class | fix edition | cre component | checks level | 1 compatible | yes The `mkp package <manifest>` command would fail with "File conflict: /omd/sites/mydevsite/local/... (already existing)" if called in a site context. Additionally, we no longer write the mkp-tools version into the "version.min_required" field of the manifest template. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # mkp-tool: CLIs 'package' command key | value ---------- | --- date | 2024-04-23T11:57:59+00:00 - version | 2.3.0b7 ? -- + version | 2.3.0 class | fix edition | cre component | checks level | 1 compatible | yes The `mkp package <manifest>` command would fail with "File conflict: /omd/sites/mydevsite/local/... (already existing)" if called in a site context. Additionally, we no longer write the mkp-tools version into the "version.min_required" field of the manifest template.

5 months, 2 weeks

← Newer
1
...
9
10
11
12
13
14
15
...
55
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 May 2024