Checkmk werks level1 December 2013

checkmk-werks-lvl1@lists.checkmk.com

7 participants
169 discussions

Check_MK Werk 0104: mssql: Server instances with underline in name are now supported.

by Bastian Kuhn

ID: 0104 Title: mssql: Server instances with underline in name are now supported. Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.3i8 Thanks to a patch from H.Schniggendiller

10 years, 9 months

Check_MK Werk 0239: Fixed incorrect html formatting when displaying host or service comments

by Andreas Boesl

ID: 0239 Title: Fixed incorrect html formatting when displaying host or service comments Component: Multisite Level: 1 Class: Bug Fix Version: 1.2.3i8 The comment icon in a multisite view was not drawn correctly whenever a comment for this host or service had a single quote.

10 years, 9 months

Check_MK Werk 0305: apache_status: Fixed exception when agent reports HTML code as apache-status data

by Lars Michelsen

ID: 0305 Title: apache_status: Fixed exception when agent reports HTML code as apache-status data Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.3i8 When the apache-status module is not enabled or the webserver is somehow missconfigured, the agents HTTP request to the apache-status URL might return HTML code instead of the expected textual response. Added code to detect HTML code and skip the webserver instance in this case.

10 years, 9 months

Check_MK Werk 0306: esx_vsphere_counters: added missing ramdisk levels sfcbtickets

by Lars Michelsen

ID: 0306 Title: esx_vsphere_counters: added missing ramdisk levels sfcbtickets Component: Checks & Agents Level: 1 Class: New Feature Version: 1.2.3i8

10 years, 9 months

Check_MK Werk 0304: Escaping several unwanted chars from incoming log messages

by Lars Michelsen

ID: 0304 Title: Escaping several unwanted chars from incoming log messages Component: Event Console Level: 1 Class: Bug Fix Version: 1.2.3i8 There are several kind of chars which are not wanted to be included in log messages. For example the null byte is nothing to be expected in log messages. We simply remove those chars now from the log messages. Single log lines do not contain new line chars (\n), since they are already processed as single lines. But snmp traps might contain those chars, which might break e.g. processing the log history (resulting in error messages "Invalid line XX in history file..."). The newline chars are now simply removed from the incoming data. This might change incoming values, but this seems to be better than before. In future, when trap the parsing/processing code is extended by single value matching etc., we might be able to clean this up.

10 years, 9 months

Check_MK Werk 0303: Old log entries were shown in event history first

by Lars Michelsen

ID: 0303 Title: Old log entries were shown in event history first Component: Event Console Level: 1 Class: Bug Fix Version: 1.2.3i8 In previous versions, when the event history views had a limit applied, like it is configured by default, it happened that too old entries were read first. When reaching the limit of entries, the processing stopped and newer events were ignored. The order of the log files during processing has now been changed.

10 years, 9 months

Check_MK Werk 0302: Fixed highlight of choosen elements in foldertee/views snapin in Chrome/IE

by Lars Michelsen

ID: 0302 Title: Fixed highlight of choosen elements in foldertee/views snapin in Chrome/IE Component: Multisite Level: 1 Class: Bug Fix Version: 1.2.3i8

10 years, 9 months

Check_MK Werk 0057: Fix exception in WATO host editor on custom tag without topic

by Mathias Kettner

ID: 0057 Title: Fix exception in WATO host editor on custom tag without topic Component: WATO Level: 2 Class: Bug Fix Version: 1.2.3i8 When you've defined a host tag group in WATO that has no topic, then the host edit dialog would be interrupted with an exception. A simple workaround to this is to alwasy define a topic. The problem has now been fixed. It had shortly been introduced by fixing a problem appearing when you used a slash in the name of a tag group.

10 years, 9 months

Check_MK Werk 0301: Handling messages of special syslog format correctly

by Lars Michelsen

ID: 0301 Title: Handling messages of special syslog format correctly Component: Event Console Level: 1 Class: New Feature Version: 1.2.3i8 The syslog RFCs allow different formats of syslog messages. The message parsing code in the event console does support several formats and should be able to deal with all formats allowed by the specifications. However, one format was not supported in past versions. Those messages were simply dropped and only seen in the logs of the event console, when rule execution debugging is enabled. These log entries look as follows: <tt><5>SYSTEM_INFO: [WLAN-1] Performing Background Scan : channel 12, active, 28 TU</tt> The specific part here is the missing date/time and missing hostname information, which is sent by most syslog clients. The parser has been changed to be able to parse this format. The event console adds the current date/time to the event and the IP address of the sending client as host information.

10 years, 9 months

Check_MK Werk 0300: cisco_fru_power: Trying not to inventorize not plugged in FRUs

by Lars Michelsen

ID: 0300 Title: cisco_fru_power: Trying not to inventorize not plugged in FRUs Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.3i8 In the previous version, the check did inventorize all FRUs reported by the device. The devices also send information for slots which have no FRU plugged in. This change tries to ignore all not plugged in slots.

10 years, 9 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 December 2013