Checkmk werks level2

checkmk-werks-lvl2@lists.checkmk.com

1 participants
1349 discussions

[2.3.0] Checkmk Werk 16839 created: mk-sql ensures instance name is correct

by Checkmk werks level 2

[//]: # (werk v2) # mk-sql ensures instance name is correct key | value ---------- | --- date | 2024-06-05T11:27:42+00:00 version | 2.3.0p6 class | feature edition | cee component | checks level | 2 compatible | no The plugin verifies whether the name of the instance at the specified address matches the name indicated in the config. If the name specified in the config does not match the instance name that responds, the monitoring of this instance will return an error. Example: The config mistakenly indicates that the `SQLEXPRESS` instance is located at `localhost:1433`, whereas the `MSSQLSERVER` instance is actually located at this address. Previously, the instance `MSSQLSERVER` were mistakenly monitored as `SQLEXPRESS`. Starting from this release, this error has been corrected. You need to correct the config if your config contained bad data.

3 months, 1 week

[2.3.0] Checkmk Werk 16839 deleted: mk-sql ensures instance name is correct

by Checkmk werks level 2

Werk 16839 was deleted. The following Werk is no longer relevant. [//]: # (werk v2) # mk-sql ensures instance name is correct key | value ---------- | --- date | 2024-06-05T11:27:42+00:00 version | 2.3.0p6 class | feature edition | cee component | checks level | 2 compatible | no The plugin verifies whether the name of the instance at the specified address matches the name indicated in the config. If the name specified in the config does not match the instance name that responds, the monitoring of this instance will return an error. Example: The config mistakenly indicates that the `SQLEXPRESS` instance is located at `localhost:1433`, whereas the `MSSQLSERVER` instance is actually located at this address. Previously, the instance `MSSQLSERVER` were mistakenly monitored as `SQLEXPRESS`. Starting from this release, this error has been corrected. You need to correct the config if your config contained bad data.

3 months, 1 week

[2.3.0] Checkmk Werk 16839 created: mk-sql ensures instance name is correct

by Checkmk werks level 2

3 months, 1 week

[2.3.0] Checkmk Werk 16882 created: Fix performance issues when processing performance data (process_perfdata.pl) and missing metric data

by Checkmk werks level 2

[//]: # (werk v2) # Fix performance issues when processing performance data (process_perfdata.pl) and missing metric data key | value ---------- | --- date | 2024-05-22T13:57:02+00:00 version | 2.3.0p3 class | fix edition | cre component | omd level | 3 compatible | yes This werk affects all users of Checkmk Raw. You might have perceived a severe performance degradation in Checkmk 2.3.0 and a lot of errors in the NPCD log. This was due to missing RRD packages and thus expensive fall-back computations. This werk fixes a performance issue in combination with potentially missing metric data, which can result in gaps in the service graphs.

3 months, 3 weeks

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

3 months, 3 weeks

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

3 months, 3 weeks

[2.3.0] Checkmk Werk 15843 adapted: mk_oracle(ps1): Follow-up to privilege escalation fix

by Checkmk werks level 2

Werk 15843 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # mk_oracle(ps1): Follow-up to privilege escalation fix key | value ---------- | --- compatible | no version | 2.3.0b4 date | 2024-04-05T11:02:27+00:00 level | 2 class | fix component | checks edition | cre You might be affected by this Werk if you use <tt>mk_oracle</tt> on Windows. Werk <a href="https://checkmk.com/werk/16232">Werk #16232</a> introduced a regression, thereby disrupting Oracle monitoring on Windows. This Werk addresses above mentioned issue that affects versions 2.1.0p41, 2.2.0p24, and 2.3.0b4. Since this release, Oracle monitoring on Windows is fully supported under either of the following conditions: 1. The monitoring is performed using an account without administrator rights. 2. Specific Oracle executable binaries — namely, <tt>sqlplus.exe</tt>, <tt>tnsping.exe</tt> and, if presented, <tt>crsctl.exe</tt> - are not modifiable by non-admin users. If you are still unable to monitor Oracle, for example, you can't use an unprivileged account for monitoring and changing of permission is not possible, consider one of the following actions: 1. Enable <tt>Run as local group</tt> for group <tt>Administrators</tt> in <tt>Run plugins and local checks using non-system account</tt> ruleset. 2. Adjust <tt>Oracle Binaries Permissions Check</tt> settings in <tt>ORACLE databases (Linux, Solaris, AIX, Windows)</tt> ruleset. More information about can be found at <a href="https://checkmk.atlassian.net/wiki/x/AQA1B">here</a>. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # mk_oracle(ps1): Follow-up to privilege escalation fix key | value ---------- | --- compatible | no version | 2.3.0b4 date | 2024-04-05T11:02:27+00:00 level | 2 class | fix component | checks edition | cre You might be affected by this Werk if you use <tt>mk_oracle</tt> on Windows. Werk <a href="https://checkmk.com/werk/16232">Werk #16232</a> introduced a regression, thereby disrupting Oracle monitoring on Windows. This Werk addresses above mentioned issue that affects versions 2.1.0p41, 2.2.0p24, and 2.3.0b4. - Since this release, Oracle monitoring on Windows is fully supported under ? - + Since this release, Oracle monitoring on Windows is fully supported under - condition you use an account without administrator rights or the certain - executable binaries, <tt>sqlplus.exe</tt>, <tt>tnsping.exe</tt> and, if - presented, <tt>crsctl.exe</tt> are write-protected, with the possible - exception being the Administrator. + either of the following conditions: + 1. The monitoring is performed using an account without administrator rights. + 2. Specific Oracle executable binaries — namely, <tt>sqlplus.exe</tt>, + <tt>tnsping.exe</tt> and, if presented, <tt>crsctl.exe</tt> - are not modifiable + by non-admin users. - If you are unable or prefer not to use an unprivileged account then you may - need to adjust permissions for above mentioned binaries: remove <tt>Write</tt>, - <tt>Full Control</tt> and <tt>Modify</tt> permissions for any non-Administrator - user and group. + If you are still unable to monitor Oracle, for example, you can't use an + unprivileged account for monitoring and changing of permission is not possible, + consider one of the following actions: + 1. Enable <tt>Run as local group</tt> for group <tt>Administrators</tt> in + <tt>Run plugins and local checks using non-system account</tt> ruleset. + 2. Adjust <tt>Oracle Binaries Permissions Check</tt> settings in <tt>ORACLE databases (Linux, + Solaris, AIX, Windows)</tt> ruleset. More information about can be found at <a href="https://checkmk.atlassian.net/wiki/x/AQA1B">here</a>.

3 months, 3 weeks

[2.3.0] Checkmk Werk 15327 created: mk_oracle: Follow-up to privilege escalation fix

by Checkmk werks level 2

[//]: # (werk v2) # mk_oracle: Follow-up to privilege escalation fix key | value ---------- | --- compatible | no version | 2.3.0b6 date | 2024-04-04T07:59:38+00:00 level | 2 class | fix component | checks edition | cre You might be affected by this Werk if you use <tt>mk_oracle</tt> on a unix system. You might be affected by this Werk if you use oracle wallet to connect to your database. You are definitively affected by this Werk if you use oracle wallet to connect to your database and used the instructions of our official documentation to setup your configuration. This Werk fixes connection problems introduced with 2.1.0p41, 2.2.0p24 and 2.3.0b4. Since <a href="https://checkmk.com/werk/16232">Werk #16232</a> we switch to a unprivileged user when executing oracle binaries. This causes problems when using an oracle wallet as the unprivileged user might not be able to access files defining the connection details and credentials. We introduced an additional permission check to the <code>-t</code> "Just check the connection" option of <code>mk_oracle</code>. It should help you modifying the permissions to continue using <code>mk_oracle</code> with oracle wallet. You can execute it with the following command: <pre> MK_CONFDIR=/etc/check_mk/ MK_VARDIR=/var/lib/check_mk_agent /usr/lib/check_mk_agent/plugins/mk_oracle --no-spool -t </pre> The path to mk_oracle might be different if you execute it asynchronously. For a 60 second interval the path would be <code>/usr/lib/check_mk_agent/plugins/60/mk_oracle</code> The script will test permissions of the files needed to connect to the database. It boils down to the following: <code>mk_oracle</code> will switch to the owner of <code>$ORACLE_HOME/bin/sqlplus</code> before executing <code>sqlplus</code>. So this user has to have the following permissions: <ul> <li>read <code>$TNS_ADMIN/sqlnet.ora</code></li> <li>read <code>$TNS_ADMIN/tnsnames.ora</code></li> <li>execute the wallet folder (<code>/etc/check_mk/oracle_wallet</code> if followed the official documentation)</li> <li>read files inside the wallet folder (<code>/etc/check_mk/oracle_wallet/*</code> if followed the official documentation)</li> </ul> Beside that we also fixed some bash syntax errors we introduced with <a href="https://checkmk.com/werk/16232">Werk #16232</a>. See <a href="https://checkmk.atlassian.net/wiki/spaces/KB/pages/70582273/Troubleshooting…">Troubleshooting mk_oracle for Windows and Linux</a> for more information about troubleshooting this problem.

3 months, 3 weeks

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

by Checkmk werks level 2

[//]: # (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 database monitoring, see werk 15842 Enhanced MS SQL Server monitoring. The new plugin extends the functionality of the `Microsoft SQL Server (Windows)` adding more options and features. 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 server to monitor remote MSSQL servers over the network. The previous rule `Microsoft SQL Server (Windows)` is deprecated and isn't applied anymore.

3 months, 3 weeks

[2.3.0] Checkmk Werk 15843 adapted: mk_oracle(ps1): Follow-up to privilege escalation fix

by Checkmk werks level 2

Werk 15843 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # mk_oracle(ps1): Follow-up to privilege escalation fix key | value ---------- | --- compatible | no version | 2.3.0b4 date | 2024-04-05T11:02:27+00:00 level | 2 class | fix component | checks edition | cre You might be affected by this Werk if you use <tt>mk_oracle</tt> on Windows. Werk <a href="https://checkmk.com/werk/16232">Werk #16232</a> introduced a regression, thereby disrupting Oracle monitoring on Windows. This Werk addresses above mentioned issue that affects versions 2.1.0p41, 2.2.0p24, and 2.3.0b4. Since this release, Oracle monitoring on Windows is fully supported under condition you use an account without administrator rights or the certain executable binaries, <tt>sqlplus.exe</tt>, <tt>tnsping.exe</tt> and, if presented, <tt>crsctl.exe</tt> are write-protected, with the possible exception being the Administrator. If you are unable or prefer not to use an unprivileged account then you may need to adjust permissions for above mentioned binaries: remove <tt>Write</tt>, <tt>Full Control</tt> and <tt>Modify</tt> permissions for any non-Administrator user and group. More information about can be found at <a href="https://checkmk.atlassian.net/wiki/x/AQA1B">here</a>. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # mk_oracle(ps1): Follow-up to privilege escalation fix key | value ---------- | --- compatible | no - version | 2.3.0b5 ? ^ + version | 2.3.0b4 ? ^ date | 2024-04-05T11:02:27+00:00 level | 2 class | fix component | checks edition | cre You might be affected by this Werk if you use <tt>mk_oracle</tt> on Windows. Werk <a href="https://checkmk.com/werk/16232">Werk #16232</a> introduced a regression, thereby disrupting Oracle monitoring on Windows. This Werk addresses above mentioned issue that affects versions 2.1.0p41, 2.2.0p24, and 2.3.0b4. Since this release, Oracle monitoring on Windows is fully supported under condition you use an account without administrator rights or the certain executable binaries, <tt>sqlplus.exe</tt>, <tt>tnsping.exe</tt> and, if presented, <tt>crsctl.exe</tt> are write-protected, with the possible exception being the Administrator. If you are unable or prefer not to use an unprivileged account then you may need to adjust permissions for above mentioned binaries: remove <tt>Write</tt>, <tt>Full Control</tt> and <tt>Modify</tt> permissions for any non-Administrator user and group. More information about can be found at <a href="https://checkmk.atlassian.net/wiki/x/AQA1B">here</a>.

3 months, 3 weeks

← Newer
1
2
3
4
5
6
7
8
9
...
135
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level2