Checkmk werks level1 September 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
218 discussions

[2.4.0] Checkmk Werk 16778 created: fortisandbox plugin: expand monitored models

by Checkmk werks level 1

[//]: # (werk v2) # fortisandbox plugin: expand monitored models key | value ---------- | --- date | 2024-09-26T11:57:53+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 1 compatible | yes Previously, the fortisandbox plugins discovered and monitored only the Fortinet _fsa3000E_ devices. With this change, the plugin monitors all available models discoverable under the oid _1.3.6.1.4.1.12356.118.1._.

1 week, 1 day

[2.2.0] Checkmk Werk 17259 created: Fix mismatching network interface and switch port services

by Checkmk werks level 1

Title: Fix mismatching network interface and switch port services Class: fix Compatible: incomp Component: checks Date: 1727275034 Edition: cre Level: 1 Version: 2.2.0p35 When configuring network interfaces to be discovered by alias or description (rule "Network interface and switch port discovery"), there was a chance of a mismatch between the discovered service item and the interface checked by the service. This happened if the alias or description of one interface matched the index of another interface. For example, if the interface discovery is configured to discover interfaces by alias, then the service "Interface 5" is supposed to check the interface with the alias "5". Instead, it checked the interface with the index 5. <strong>Compatibility Hint</strong> To apply the fix, you need to remove the interface services and rediscover them. If you do not remove and rediscover them, the fix will not be applied and you might still have mismatched services.

1 week, 3 days

[2.4.0] Checkmk Werk 17259 created: Fix mismatching network interface and switch port services

by Checkmk werks level 1

[//]: # (werk v2) # Fix mismatching network interface and switch port services key | value ---------- | --- date | 2024-09-25T14:37:14+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | no When configuring network interfaces to be discovered by alias or description (rule "Network interface and switch port discovery"), there was a chance of a mismatch between the discovered service item and the interface checked by the service. This happened if the alias or description of one interface matched the index of another interface. For example, if the interface discovery is configured to discover interfaces by alias, then the service "Interface 5" is supposed to check the interface with the alias "5". Instead, it checked the interface with the index 5. **Compatibility Hint** To apply the fix, you need to remove the interface services and rediscover them. If you do not remove and rediscover them, the fix will not be applied and you might still have mismatched services.

1 week, 3 days

[2.3.0] Checkmk Werk 17259 created: Fix mismatching network interface and switch port services

by Checkmk werks level 1

[//]: # (werk v2) # Fix mismatching network interface and switch port services key | value ---------- | --- date | 2024-09-25T14:37:14+00:00 version | 2.3.0p18 class | fix edition | cre component | checks level | 1 compatible | no When configuring network interfaces to be discovered by alias or description (rule "Network interface and switch port discovery"), there was a chance of a mismatch between the discovered service item and the interface checked by the service. This happened if the alias or description of one interface matched the index of another interface. For example, if the interface discovery is configured to discover interfaces by alias, then the service "Interface 5" is supposed to check the interface with the alias "5". Instead, it checked the interface with the index 5. **Compatibility Hint** To apply the fix, you need to remove the interface services and rediscover them. If you do not remove and rediscover them, the fix will not be applied and you might still have mismatched services.

1 week, 4 days

[2.3.0] Checkmk Werk 17257 adapted: postfix_mailq: Fix service reporting missing item after upgrade

by Checkmk werks level 1

Werk 17257 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # postfix_mailq: Fix service reporting missing item after upgrade key | value ---------- | --- date | 2024-09-18T11:36:57+00:00 version | 2.3.0p18 class | fix edition | cre component | checks level | 1 compatible | no In Werk #16377 we renamed the postfix_mailq services in the case where only a single such service existed. There was a bug which occured in combination with various linux agents where the service would show up as UNKNOWN after applying an update, even after rediscovering. With this werk, the postfix_mailq service will no longer show up as UNKNOWN. **Incompatibility** In various linux agents, the postfix_mailq service will report state UNKNOWN saying "Item not found in monitoring data" after upgrading. If that is the case in your environment, simply rediscover the services. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # postfix_mailq: Fix service reporting missing item after upgrade key | value ---------- | --- date | 2024-09-18T11:36:57+00:00 - version | 2.3.0p17 ? ^ + version | 2.3.0p18 ? ^ class | fix edition | cre component | checks level | 1 compatible | no In Werk #16377 we renamed the postfix_mailq services in the case where only a single such service existed. There was a bug which occured in combination with various linux agents where the service would show up as UNKNOWN after applying an update, even after rediscovering. With this werk, the postfix_mailq service will no longer show up as UNKNOWN. **Incompatibility** In various linux agents, the postfix_mailq service will report state UNKNOWN saying "Item not found in monitoring data" after upgrading. If that is the case in your environment, simply rediscover the services.

1 week, 4 days

[2.1.0] Checkmk Werk 16871 created: smart: Monitor SATA disks connected via HBA

by Checkmk werks level 1

Title: smart: Monitor SATA disks connected via HBA Class: fix Compatible: compat Component: checks Date: 1726577620 Edition: cre Level: 1 Version: 2.1.0p48 Previously, SATA disks connected via HBA weren't monitored by the smart agent plugin. Now, they are monitored the same way as other ATA disks.

1 week, 5 days

[2.2.0] Checkmk Werk 16871 created: smart: Monitor SATA disks connected via HBA

by Checkmk werks level 1

Title: smart: Monitor SATA disks connected via HBA Class: fix Compatible: compat Component: checks Date: 1726577620 Edition: cre Level: 1 Version: 2.2.0p35 Previously, SATA disks connected via HBA weren't monitored by the smart agent plugin. Now, they are monitored the same way as other ATA disks.

1 week, 5 days

[2.2.0] Checkmk Werk 17258 created: Fix host renaming failing when host is node of cluster

by Checkmk werks level 1

Title: Fix host renaming failing when host is node of cluster Class: fix Compatible: compat Component: wato Date: 1726756410 Edition: cre Level: 1 Version: 2.2.0p35 There was a bug when renaming a host which is a node of a cluster and inside a folder. The cluster would show the new name but the host itself would keep its old name. With this werk, hosts are now properly renamed as expected.

1 week, 5 days

[2.3.0] Checkmk Werk 16871 created: smart: Monitor SATA disks connected via HBA

by Checkmk werks level 1

[//]: # (werk v2) # smart: Monitor SATA disks connected via HBA key | value ---------- | --- compatible | yes version | 2.3.0p18 date | 2024-09-17T12:53:40+00:00 level | 1 class | fix component | checks edition | cre Previously, SATA disks connected via HBA weren't monitored by the smart agent plugin. Now, they are monitored the same way as other ATA disks.

1 week, 5 days

[2.3.0] Checkmk Werk 17258 created: Fix host renaming failing when host is node of cluster

by Checkmk werks level 1

[//]: # (werk v2) # Fix host renaming failing when host is node of cluster key | value ---------- | --- compatible | yes version | 2.3.0p18 date | 2024-09-19T14:33:30+00:00 level | 1 class | fix component | wato edition | cre There was a bug when renaming a host which is a node of a cluster and inside a folder. The cluster would show the new name but the host itself would keep its old name. With this werk, hosts are now properly renamed as expected.

1 week, 5 days

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 September 2024