Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
16154 discussions

[2.3.0] Checkmk Werk 16682 created: Ruleset API: Fix migration with scaling of SimpleLevels

by Checkmk werks level 1

[//]: # (werk v2) # Ruleset API: Fix migration with scaling of SimpleLevels key | value ---------- | --- date | 2024-04-17T11:19:36+00:00 version | 2.3.0b6 class | fix edition | cre component | checks level | 1 compatible | no This change is relevant to plugin developers The migration helper functions `migrate_to_integer_simple_levels` and `migrate_to_float_simple_levels` for `SimpleLevels` currently apply the scaling factor (if given) every time the migration is run, meaning also to the already migrated value. This means any rule where these helpers are used with a scaling factor will have incorrect values and will have to be manually corrected. No shipped rules are affected by this.

5 months, 2 weeks

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

5 months, 2 weeks

[2.3.0] Checkmk Werk 16423 created: mk_postgres.py: Add 'PG_BINARY_PATH' to Bakery Rule

by Checkmk werks level 1

[//]: # (werk v2) # mk_postgres.py: Add 'PG_BINARY_PATH' to Bakery Rule key | value ---------- | --- date | 2024-04-16T15:15:06+00:00 version | 2.3.0b5 class | feature edition | cee component | agents level | 1 compatible | yes [Werk #15619](https://checkmk.com/werk/15619) added support for reading `PG_BINARY_PATH` from `postgres.cfg`. This Werk allows setting this value with the agent bakery.

5 months, 2 weeks

[2.3.0] Checkmk Werk 16690 created: pfsense_if: stale services in 2.3 beta

by Checkmk werks level 1

[//]: # (werk v2) # pfsense_if: stale services in 2.3 beta key | value ---------- | --- date | 2024-04-17T11:38:38+00:00 version | 2.3.0b5 class | fix edition | cre component | checks level | 1 compatible | yes

5 months, 2 weeks

[2.3.0] Checkmk Werk 15199 created: Update OpenSSL to version 3.0.13

by Checkmk werks level 1

[//]: # (werk v2) # Update OpenSSL to version 3.0.13 key | value ---------- | --- date | 2024-04-17T10:08:23+00:00 version | 2.3.0b6 class | security edition | cre component | omd level | 1 compatible | yes OpenSSL was updated to version 3.0.13. OpenSSL 3 uses requirements regarding allowed configurations, such as allowed ciphers, renegotiation, and so on. In some scenarios, this can break monitoring for hosts with TLS configurations that are no longer considered secure. We have published a blog post to help you mitigate these issues, should they affect you: https://checkmk.com/blog/how-monitor-servers-broken-tls-checkmk. To aid automated scanning we assign a CVSS score of 0.0 (None) (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N).

5 months, 2 weeks

[2.3.0] Checkmk Werk 16588 created: time_periods: Fix timeperiod iCalendar (ics) import

by Checkmk werks level 1

[//]: # (werk v2) # time_periods: Fix timeperiod iCalendar (ics) import key | value ---------- | --- date | 2024-04-17T09:19:29+00:00 version | 2.3.0b6 class | fix edition | cre component | wato level | 1 compatible | yes This Werk solves a problem with importing events that take more than one day. Before this Werk, only the first day of the event was imported. Now all days involved are imported.

5 months, 2 weeks

[2.3.0] Checkmk Werk 16600 adapted: NetApp via WebAPI: deprecate agent and plugins

by Checkmk werks level 1

Werk 16600 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # NetApp via WebAPI: deprecate agent and plugins key | value ---------- | --- date | 2024-03-15T14:10:08+00:00 version | 2.3.0b4 class | fix edition | cre component | checks level | 1 compatible | yes As of Checkmk version 2.3.0b4, the special agent "NetApp via WebAPI" (_agent_netapp_) is deprecated and will be removed in a future version. This also affects the associated checks and inventory plugins: - NetApp Filer: Cluster-Mode CPU Utilization (_netapp_api_aggr_) - NetApp Ontap Filer: 7Mode Cluster Status (_netapp_api_cluster_) - NetApp API Connection (_netapp_api_connection_) - NetApp Filer: Cluster-Mode CPU Utilization (_netapp_api_cpu_) - NetApp Clustermode Filer: NVRAM Battery (_netapp_api_cpu_nvram_bat_) - NetApp Filer: 7Mode Global CPU Utilization (_netapp_api_cpu_utilization_) - NetApp Filer: Disk (_Summarynetapp_api_disk_summary_) - NetApp Filer Clustermode: PSU Fault Info (_netapp_api_environment_) - NetApp Filer Clustermode: System Electrical Current (_netapp_api_environment_current_) - NetApp Filer Clustermode: Fan Fault Info (_netapp_api_environment_fan_faults_) - NetApp Filer Clustermode: System Fan Speed (_netapp_api_environment_fans_) - NetApp Filer Clustermode: System Temperature (_netapp_api_environment_temperature_) - NetApp Filer Clustermode: System Electrical Voltage (_netapp_api_environment_voltage_) - NetApp Filer: FANs (_netapp_api_fan_) - NetApp Filer: FANs Summary (_netapp_api_fan_summary_) - NetApp Cluster-Mode: State of Fibrechannel Interfaces (_netapp_api_fcp_) - NetApp Filer: State of Network Interfaces (_netapp_api_if_) - NetApp Filer: Version Info (_netapp_api_info_) - NetApp Filer: Used Space of LUNs (_netapp_api_luns_) - NetApp Filer: Ports (_netapp_api_ports_) - NetApp Filer 7Mode: Protocols (_netapp_api_protocol_) - NetApp Filer: Power Supplies (_netapp_api_psu_) - NetApp Filer: Power Supplies Summary (_netapp_api_psu_summary_) - NetApp Filer: Used Space of qtrees in Volumes (_netapp_api_qtree_quota_) - NetApp Filer: Used Space in Snapshots of Volumes (_netapp_api_snapshots_) - NetApp Filer: Snapvault/Snapmirror Lag-time (_netapp_api_snapvault_) - NetApp Filer: Overall System Health (_netapp_api_status_) - NetApp Filer: Systemtime (_netapp_api_systemtime_) - NetApp Filer: Temperature Sensors (_netapp_api_temp_) - NetApp Filer 7Mode: vFiler CPU Utilization (_netapp_api_vf_stats_) - NetApp Filer: vFiler Traffic (_netapp_api_vf_stats_traffic_) - NetApp Filer: vFiler Status (_netapp_api_vf_status_) - NetApp Filer: Used Space and Traffic of Volumes (_netapp_api_volumes_) - NetApp Filer: vServer Status (_netapp_api_vs_status_) - NetApp Filer: vServer Traffic Summary (_netapp_api_vs_traffic_) ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) - # netapp_api: deprecate agent and plugins ? ^ ^ ^ ^^ + # NetApp via WebAPI: deprecate agent and plugins ? ^ ^ ^^^ ^^^^^^^ key | value ---------- | --- date | 2024-03-15T14:10:08+00:00 version | 2.3.0b4 class | fix edition | cre component | checks level | 1 compatible | yes - As of Checkmk version 2.3.0b4, the special agent "netapp_api" is deprecated ? ^^^^ + As of Checkmk version 2.3.0b4, the special agent "NetApp via WebAPI" (_agent_netapp_) is deprecated ? +++++++++++++++++++++++++++ ^ and will be removed in a future version. This also affects the associated checks and inventory plugins: - - netapp_api_aggr - - netapp_api_cluster - - netapp_api_connection - - netapp_api_cpu - - netapp_api_cpu_nvram_bat - - netapp_api_cpu_utilization - - netapp_api_disk_summary - - netapp_api_environment - - netapp_api_environment_current - - netapp_api_environment_fan_faults - - netapp_api_environment_fans - - netapp_api_environment_temperature - - netapp_api_environment_voltage - - netapp_api_fan - - netapp_api_fan_summary - - netapp_api_fcp - - netapp_api_if - - netapp_api_info - - netapp_api_luns - - netapp_api_ports - - netapp_api_protocol - - netapp_api_psu - - netapp_api_psu_summary - - netapp_api_qtree_quota - - netapp_api_snapshots - - netapp_api_snapvault - - netapp_api_status - - netapp_api_systemtime - - netapp_api_temp - - netapp_api_vf_stats - - netapp_api_vf_stats_traffic - - netapp_api_vf_status - - netapp_api_volumes - - netapp_api_vs_status - - netapp_api_vs_traffic + - NetApp Filer: Cluster-Mode CPU Utilization (_netapp_api_aggr_) + - NetApp Ontap Filer: 7Mode Cluster Status (_netapp_api_cluster_) + - NetApp API Connection (_netapp_api_connection_) + - NetApp Filer: Cluster-Mode CPU Utilization (_netapp_api_cpu_) + - NetApp Clustermode Filer: NVRAM Battery (_netapp_api_cpu_nvram_bat_) + - NetApp Filer: 7Mode Global CPU Utilization (_netapp_api_cpu_utilization_) + - NetApp Filer: Disk (_Summarynetapp_api_disk_summary_) + - NetApp Filer Clustermode: PSU Fault Info (_netapp_api_environment_) + - NetApp Filer Clustermode: System Electrical Current (_netapp_api_environment_current_) + - NetApp Filer Clustermode: Fan Fault Info (_netapp_api_environment_fan_faults_) + - NetApp Filer Clustermode: System Fan Speed (_netapp_api_environment_fans_) + - NetApp Filer Clustermode: System Temperature (_netapp_api_environment_temperature_) + - NetApp Filer Clustermode: System Electrical Voltage (_netapp_api_environment_voltage_) + - NetApp Filer: FANs (_netapp_api_fan_) + - NetApp Filer: FANs Summary (_netapp_api_fan_summary_) + - NetApp Cluster-Mode: State of Fibrechannel Interfaces (_netapp_api_fcp_) + - NetApp Filer: State of Network Interfaces (_netapp_api_if_) + - NetApp Filer: Version Info (_netapp_api_info_) + - NetApp Filer: Used Space of LUNs (_netapp_api_luns_) + - NetApp Filer: Ports (_netapp_api_ports_) + - NetApp Filer 7Mode: Protocols (_netapp_api_protocol_) + - NetApp Filer: Power Supplies (_netapp_api_psu_) + - NetApp Filer: Power Supplies Summary (_netapp_api_psu_summary_) + - NetApp Filer: Used Space of qtrees in Volumes (_netapp_api_qtree_quota_) + - NetApp Filer: Used Space in Snapshots of Volumes (_netapp_api_snapshots_) + - NetApp Filer: Snapvault/Snapmirror Lag-time (_netapp_api_snapvault_) + - NetApp Filer: Overall System Health (_netapp_api_status_) + - NetApp Filer: Systemtime (_netapp_api_systemtime_) + - NetApp Filer: Temperature Sensors (_netapp_api_temp_) + - NetApp Filer 7Mode: vFiler CPU Utilization (_netapp_api_vf_stats_) + - NetApp Filer: vFiler Traffic (_netapp_api_vf_stats_traffic_) + - NetApp Filer: vFiler Status (_netapp_api_vf_status_) + - NetApp Filer: Used Space and Traffic of Volumes (_netapp_api_volumes_) + - NetApp Filer: vServer Status (_netapp_api_vs_status_) + - NetApp Filer: vServer Traffic Summary (_netapp_api_vs_traffic_)

5 months, 2 weeks

[2.3.0] Checkmk Werk 16606 created: agent_netapp_ontap: handle shelves without elements

by Checkmk werks level 1

[//]: # (werk v2) # agent_netapp_ontap: handle shelves without elements key | value ---------- | --- date | 2024-04-10T12:26:35+00:00 version | 2.3.0b5 class | fix edition | cre component | checks level | 1 compatible | yes The agent did not handle the cases where shelves had no fans, temperature sensors or PSUs. This led to crashes during the agent execution. With this werk we now correctly handle these scenarios and the corresponding services are not discovered if no items are found.

5 months, 2 weeks

[2.3.0] Checkmk Werk 16695 created: Just show an error message if redis is not reachable

by Checkmk werks level 1

[//]: # (werk v2) # Just show an error message if redis is not reachable key | value ---------- | --- date | 2024-04-17T06:14:37+00:00 version | 2.3.0b6 class | fix edition | cre component | multisite level | 1 compatible | yes The mega menu search produced a crash report if redis was not reachable. Now only an error message is shown.

5 months, 2 weeks

[2.3.0] Checkmk Werk 15198 created: Brute-force protection ineffective for some login methods

by Checkmk werks level 1

[//]: # (werk v2) # Brute-force protection ineffective for some login methods key | value ---------- | --- date | 2024-04-09T12:24:12+00:00 version | 2.3.0b5 class | security edition | cre component | wato level | 1 compatible | yes Prior to this Werk, the mechanism to lock user accounts after too many failed login attempts was only effective for the web form login method. Login attempts via the REST API and basic authentication did not count towards the lockout mechanism. As a result, an attacker could try to brute-force user passwords without triggering the lockout mechanism. This Werk adds the same locking mechanism to login via the REST API and basic authentication _for human user accounts_. Note that automation accounts are remain unaffected by the lockout mechanism to avoid having them locked by malicious intent. It is therefore important to use long, random automation secrets. This issue was found during internal review. **Affected Versions**: * 2.3.0 (beta) * 2.2.0 * 2.1.0 * 2.0.0 (EOL) **Mitigations**: If updating is not possible, the brute-force attempts can be hindered by using a strong password policy. **Vulnerability Management**: We have rated the issue with a CVSS Score of 5.9 (Medium) with the following CVSS vector: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N` and assigned CVE `CVE-2024-28825`.

5 months, 2 weeks

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1