Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15969 discussions

Checkmk Werk 14553: Prometheus: Bad request url /api/v1/api/v1/status/buildinfo

by Solomon Jacobs

ID: 14553 Title: Prometheus: Bad request url /api/v1/api/v1/status/buildinfo Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 Previously, the Prometheus special agent would query endpoints, which don't exist. This would (depending on the the HTTP response of the server) result in the following error C+: [special_prometheus] Agent exited with code 1: 400 Client Error: Bad Request for url: http://127.0.0.1:8428/api/v1/api/v1/status/buildinfo(!!) C-: Moreover, the buildinfo would sometimes be incomplete. Note, the new error is a regression introduced in werk 14132. With this werk, the Prometheus agent queries the endpoints C+: /api/v1/status/buildinfo /api/v1/status/runtimeinfo C-:

2 years, 1 month

Checkmk Werk 14505: heartbeat_crm_resources: services not discovered under pacemaker version >= 2

by Lisa Pichler

ID: 14505 Title: heartbeat_crm_resources: services not discovered under pacemaker version >= 2 Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 The check heartbeat_crm_resources would not discover any services when pacemaker version >= 2 is installed on the host system. This is for example the case with RHEL8. This has been fixed. The problem was due to the fact that newer versions of pacemaker show heartbeat information in a different format.

2 years, 1 month

Checkmk Werk 14716: Local customizations might need adjustment due to structural refactorings in GUI code

by Joerg Herbel

ID: 14716 Title: Local customizations might need adjustment due to structural refactorings in GUI code Component: Setup Level: 1 Class: New feature Version: 2.2.0i1 This werk only affects users of non-tribe29 local customizations (single files and MKPs from non- tribe29 sources such as the Checkmk exchange). Two monolithic files under <tt>cmk/gui/plugins/wato/</tt> have been split up into multiple smaller files: LI: <tt>datasource_programs.py</tt>, which defined rules for configuring special agents, has been refactored into the folder <tt>datasource_programs</tt>. LI: <tt>active_checks.py</tt>, which defined rules for configuring active checks, has been refactored into the folder <tt>active_checks</tt>. Hence, any customization containing imports from any of the two dissolved files has to be adjusted. The new import paths are probably <tt>cmk.gui.plugins.wato.datasource_programs/active_checks.common</tt>. Note that this only affects non-tribe29 customizations because as of the writing of this werk, any customization produced by tribe29 will be obsolete with Checkmk 2.2.

2 years, 1 month

Checkmk Werk 14140: kemp_loadmaster_realserver: incorporate virtual services

by External contributor

ID: 14140 Title: kemp_loadmaster_realserver: incorporate virtual services Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 The Kemp LoadMaster may provide multiple server states for the same Real Server, each state corresponding to a virtual service. Previously, the check kemp_loadmaster_realserver would incorrectly assume that these states do not differ across different virtual services. With this werk, each service will display all of connected Real server states.

2 years, 1 month

Checkmk Werk 13427: ucs_rack_server_psu_voltage no longer discovers fabric interconnect PSUs

by Benedikt Seidl

ID: 13427 Title: ucs_rack_server_psu_voltage no longer discovers fabric interconnect PSUs Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 Before this change Services like "Output Voltage switch-A PSU 1" were discovered but had an unknown status.

2 years, 1 month

Checkmk Werk 14382: Don't leak LDAP server address when connection fails

by Hannes Rantzsch

ID: 14382 Title: Don't leak LDAP server address when connection fails Component: Setup Level: 1 Class: Security fix Version: 2.2.0i1 Prior to this Werk, trying to authenticate to an LDAP server that is unavailable would result in an error saying that the server could be contacted. This leaks the address of the LDAP server. In addition, it was possible to check if a user is a htpasswd user, since the LDAP connection is not attempted for these users and LDAP error is not shown. Now a generic "invalid login" message is shown to avoid this information disclosure.

2 years, 1 month

Checkmk Werk 14531: azure special agent: fix usagedetails section

by Giordano Tomassorri

ID: 14531 Title: azure special agent: fix usagedetails section Component: agents Level: 1 Class: Bug fix Version: 2.2.0i1 The usagedetails section was fetched using an api call that was no longer supported by microsoft. This werk fixes the issue and now the Cost services are working again.

2 years, 1 month

Checkmk Werk 14674: ibm csv eventlog check now compatible with IBM FlashSystem 900

by External contributor

ID: 14674 Title: ibm csv eventlog check now compatible with IBM FlashSystem 900 Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 The ibm svc eventlog check is not compatible wit hIBM FlashSystem 900 systems. Previously the check would produce a crash with the cause: "ValueError: too many values to unpack (expected 11)".

2 years, 1 month

Checkmk Werk 14672: The Ceph MGRs check now checks if epoch information is available

by External contributor

ID: 14672 Title: The Ceph MGRs check now checks if epoch information is available Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 The epoch information is not available in the ceph status information since Octopus (15.x.x). The Ceph MGRs check is now only discovered if the epoch information is available.

2 years, 1 month

Checkmk Werk 14693: clustering: Fix clustering in case of failover

by Sofia Colakovic

ID: 14693 Title: clustering: Fix clustering in case of failover Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 In case of failover, a clustered check showed "Item not found in monitoring data" instead of fetching the data from the second node. The problem was that the service was discovered on a particular node within the cluster and expected to persist on this node, instead of being fetched from other nodes in the event that a failover had occurred. This behavior was visible when the rule "Aggregation options for clustered services" was set on "Failover".

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1