Checkmk werks level1 May 2023

checkmk-werks-lvl1@lists.checkmk.com

19 participants
130 discussions

Checkmk Werk 15611: Migrate <tt>Locked by</tt> during site renamings

by External contributor

ID: 15611 Title: Migrate <tt>Locked by</tt> during site renamings Component: Site Management Level: 2 Class: Bug fix Version: 2.2.0b7 Users which execute <tt>omd mv</tt> or <tt>omd cp</tt> expect Checkmk to not only rename the site, but also migrate the existing configurations created by the <tt>Dynamic host management</tt>. Previously, if a host was created by the DCD, then the host property <tt>Creation / Locking > Locked by</tt> would not be migrated. Instead the site would show <tt>Unknown site (OLD_SITE_ID)</tt> and the host would no longer be updated by the DCD. With this Werk, the migration is done automatically during the renaming.

1 year, 4 months

Checkmk Werk 15747: Fix macro replacement in special agents

by External contributor

ID: 15747 Title: Fix macro replacement in special agents Component: config Level: 1 Class: Bug fix Version: 2.1.0p28 The use of macros was enabled for special agent parameters with werk 3721, but no longer worked in 2.1. It's fixed with this werk.

1 year, 4 months

Checkmk Werk 15266: Check plugin logwatch_ec: Improve detection of missing log files

by Rebekka Seltmann

ID: 15266 Title: Check plugin logwatch_ec: Improve detection of missing log files Component: Checks & agents Level: 1 Class: Bug fix Version: 2.3.0b1 Previously the Logwatch Event Console Forwarding service would not report log files as missing that are marked as such in the agent output: F+: <<<logwatch>>> [[[logfile:missing]]] F-: This affected logfiles that were explicitly configured to be monitored, as opposed to configurations that capture multiple logfiles at once. With this werk this has been fixed.

1 year, 4 months

Checkmk Werk 15264: Check plugins logwatch, logwatch_ec: Notify about unreadable log file

by Rebekka Seltmann

ID: 15264 Title: Check plugins logwatch, logwatch_ec: Notify about unreadable log file Component: Checks & agents Level: 1 Class: Bug fix Version: 2.3.0b1 In the Logwatch and Logwatch Event Console Forwarding Check unreadable log files (e.g. due to insufficient permissions) were previously treated the same as missing log files. With this werk, the checks will check specifically for log files that could not be read and will become {CRIT} if any are present. To configure the state for the Event Console Forwarding service when unreadable files are detected, use the option "State if a logfile cannot be read" in the rule Logwatch Event Console Forwarding.

1 year, 4 months

Checkmk Werk 15735: <tt>check_traceroute</tt>: Fix checking of routers specified by domain name

by External contributor

ID: 15735 Title: <tt>check_traceroute</tt>: Fix checking of routers specified by domain name Component: Checks & agents Level: 1 Class: Bug fix Version: 2.3.0b1 The active check <tt>check_traceroute</tt>, configurable via the ruleset Check current routing, failed to check routers specified by domain name: LI: Routers for which the active check was supposed to alert if they are not included in the route were always reported as missing, even if they were included. LI: Routers for which the active check was supposed to alert if they are included in the route were always reported as absent, even if they were included.

1 year, 4 months

Checkmk Werk 15536: IPMI sensors: consider sensor state as reported by freeipmi

by External contributor

ID: 15536 Title: IPMI sensors: consider sensor state as reported by freeipmi Component: Checks & agents Level: 1 Class: New feature Version: 2.3.0b1 This werk changes the way Checkmk derives the state of IPMI sensors from their status descriptions. Previously, Checkmk would first check the user configured parameters (IPMI sensors -> Set states of IPMI sensor status texts), and then fall back to built-in heuristics to derive the service state from the sensors status description. These heuristics missed a lot of possible "OK" states, and thus produced false positives. This situation is improved by using the sensor status interpretation provided by <tt>freeipmi</tt>, if present. The order of preference is: Use the first matching user configured state, if found. Otherwise use the status as reported by <tt>freeipmi</tt>, if it is present. If neither of these can be applied, still fall back to the built-in heuristics. In order to get the <tt>freeipmi</tt> status reported by the agent, you need to select "Sensor state" in the rule set "IPMI Sensors via Freeipmi or IPMItool".

1 year, 4 months

Checkmk Werk 15475: agent_vsphere: Fix the IPv6 address format

by External contributor

ID: 15475 Title: agent_vsphere: Fix the IPv6 address format Component: agents Level: 1 Class: Bug fix Version: 2.3.0b1

1 year, 4 months

Checkmk Werk 15535: IPMI sensors: Do not discover single absent sensors

by External contributor

ID: 15535 Title: IPMI sensors: Do not discover single absent sensors Component: Checks & agents Level: 1 Class: New feature Version: 2.3.0b1 When configured to discover one service per sensor in the rule set IPMI sensor discovery, the IPMI check plugins now ignore absent sensors. A sensor is considered absent if its status description contains any of the strings "Device Removed" "Device Absent" or "Entity Absent".

1 year, 4 months

Checkmk Werk 15491: Fix possible crash on editing pagetypes

by External contributor

ID: 15491 Title: Fix possible crash on editing pagetypes Component: Multisite Level: 1 Class: Bug fix Version: 2.2.0b8 If you edited pagetypes like topics, custom graphs, etc. and tried to save an unallowed value, e.g. float instead of integer for "Sort order", the error "UnboundLocalError: cannot access local variable 'new_page_dict' where it is not associated with a value" occurred. You will now get a message which value is wrong to correct it before saving the pagetype.

1 year, 4 months

Checkmk Werk 15483: Fix missing metric history values on edit

by Ronny Bruska

ID: 15483 Title: Fix missing metric history values on edit Component: Multisite Level: 1 Class: Bug fix Version: 2.3.0b1 The metric history is or can be used in different places, e.g. the gauge dashlet or in columns of views. If you have used e.g. a column with "Service: Metric History" in a view and edited the view again, the default value was always shown. Note: The settings were stored correctly, this was just a display bug.

1 year, 4 months

← Newer
1
...
5
6
7
8
9
10
11
12
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 May 2023