Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
16045 discussions

Checkmk Werk 11525: lnx_if: Treat only interfaces with UP and LOWER_UP (bracket info from ip address) as UP

by Simon Jess

ID: 11525 Title: lnx_if: Treat only interfaces with UP and LOWER_UP (bracket info from ip address) as UP Component: Checks & agents Level: 1 Class: Bug fix Version: 2.1.0i1 Previously we only checked {{<...,UP>}} in the bracket info and treated this interface as {{UP}} if and only if no output of ethtool is available. Please have a look at the following scenarios and how we now determine whether an interface is {{UP}}: <ul> <li>{{<BROADCAST,MULTICAST,UP,LOWER_UP>}} means that this interface has a link and is UP</li> <li>{{<NO-CARRIER,BROADCAST,MULTICAST,UP>}} means that this interface is configured and ADMIN UP but has no link</li> <li>{{<BROADCAST,MULTICAST>}} means that this interface is not configured</li> </ul>

3 years, 9 months

Checkmk Werk 11744: support case-insensitive hostname matching for multiple host match types

by Lisa Pichler

ID: 11744 Title: support case-insensitive hostname matching for multiple host match types Component: Event Console Level: 1 Class: Bug fix Version: 2.1.0i1 Hosts are matched to events in the Event Console using different specification methods: hostname, IP address, and host alias. In the event that multiple specification methods are used to query events, livestatus queries did not return events for hosts if the letter casing was inconsistent. This was caused by two mechanisms: - Preliminary filters that determine whether livestatus queries need to be performed - Host matching criteria that returned negative results This defect becomes evident when the check_mkevents Active Check is used to monitor events, and multiple items in the "Match the hosts with" option are selected ("Check event state in Event Console" ruleset). In this case, the check will return fewer events than are expected. The livestatus query now supports case-insensitive host/event matching. Please be advised that this fix may result in larger volumes of matched events. Therefore, we advise users to evaluate the implications of this fix prior to installation.

3 years, 9 months

Checkmk Werk 11916: Fix adding of graphs to custom graphs or graph collections

by Ronny Bruska

ID: 11916 Title: Fix adding of graphs to custom graphs or graph collections Component: Multisite Level: 1 Class: Bug fix Version: 2.1.0i1 Adding of graphs to custom graphs or graph collections was not possible on some browser. Furthermore, if you added a graph to custom graphs, the landing page was not the edit page of the custom graph. Both issues have been fixed.

3 years, 9 months

Checkmk Werk 11833: Pagerduty notifications: HTTP 400, "'payload.source' is missing or blank"

by External contributor

ID: 11833 Title: Pagerduty notifications: HTTP 400, "'payload.source' is missing or blank" Component: Notifications Level: 1 Class: Bug fix Version: 2.1.0i1 For hosts without an IP address, the pagerduty notification plugin failed with HTTP 400 (Bad Request), "'payload.source' is missing or blank" This has been fixed.

3 years, 9 months

Checkmk Werk 10320: Enable SAML athentication

by Alex Zurhake

ID: 10320 Title: Enable SAML athentication Component: Other Components Level: 1 Class: New feature Version: 2.1.0i1 Enable SAML athentication It is now possible to configure SAML authentication at the site apache level using mod_auth_melon. How to do this exactly will be explained separately in a user manual article. This feature is not supported in sles-12sp3, sles-12sp4 and sles-15 (missing dependencies). To use this feature please upgrade to a newer Distro.

3 years, 9 months

Checkmk Werk 11721: Allow additional tags for baked RPM agent packages

by Andreas Umbreit

ID: 11721 Title: Allow additional tags for baked RPM agent packages Component: agents Level: 1 Class: New feature Version: 2.1.0i1 The Linux RPM packages built by the agent bakery are packaged independently of any Linux distribution. Hence, the <tt>DISTRIBUTION</tt> and <tt>DISTTAG</tt> tags are left empty within the underlying RPM spec file. If you happen to need these tags, (e.g., if you employ some sort of additional deployment mechanism, that reads from these tags) you can now specify them with the help of the agent rule "Specify RPM package tags (Linux)".

3 years, 9 months

Checkmk Werk 11889: tcp_conn_stats: Missing data for datapower devices

by Moritz Kiemer

ID: 11889 Title: tcp_conn_stats: Missing data for datapower devices Component: Checks & agents Level: 1 Class: Bug fix Version: 2.1.0i1 The check plugin tcp_conn_stats was not discovered (or got no data) for datapower devices accessing the relevant data via SNMP.

3 years, 9 months

Checkmk Werk 11873: Fix exception caused by custom host attributes when saving host changes

by Lars Michelsen

ID: 11873 Title: Fix exception caused by custom host attributes when saving host changes Component: Setup Level: 1 Class: Bug fix Version: 2.1.0i1 When some kind of custom host attribute has been defined and is used in the host configuration, this may lead to an exception like this when editing or deleting hosts: <tt>Exception: AttributeError ('HostAttributeMYATTRIBUTEConcrete' object has no attribute 'is_explicit')</tt>.

3 years, 9 months

Checkmk Werk 11875: Linux agent: Fix random broken pipe error in agent output

by Lars Michelsen

ID: 11875 Title: Linux agent: Fix random broken pipe error in agent output Component: Checks & agents Level: 1 Class: Bug fix Version: 2.1.0i1 The agent output may randomly contain errors like this in the first line of the agent output "line 12: echo: write error: Broken pipe" which would confuse the Checkmk server side and result in Check_MK services reporting CRITICAL states with an error message like "Unsupported protocol version" or "Agent output is encrypted but encryption is disabled by configuration".

3 years, 9 months

Checkmk Werk 11928: Crash: When service goes Crit or Warn but the respective level is not defined (None)

by Lukas Lengler

ID: 11928 Title: Crash: When service goes Crit or Warn but the respective level is not defined (None) Component: Checks & agents Level: 1 Class: Bug fix Version: 2.1.0i1 If the upper levels for a service are defined for example as (None, 50.0) and the service goes {CRIT} the service would crash because it cannot display None. This would only occur for legacy check plugins. Now the string "never" is diplayed instead of the respective value.

3 years, 9 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1