Checkmk werks level1 May 2014

checkmk-werks-lvl1@lists.checkmk.com

5 participants
57 discussions

Check_MK Werk 0956: fast_lta_headunit.status, fast_lta_headunit.replication: New checks for FAST LTA Storage Systems

by Bernd Stroessenreuther

ID: 0956 Title: fast_lta_headunit.status, fast_lta_headunit.replication: New checks for FAST LTA Storage Systems Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.5i3

10 years, 3 months

Check_MK Werk 0973: Renaming of hosts via WATO

by Mathias Kettner

ID: 0973 Title: Renaming of hosts via WATO Component: WATO Level: 2 Class: New Feature Version: 1.2.5i3 WATO has now a new function Rename Host. You will find a button with that name in the Properties of a host. It allows a renaming of an existing host. Before you can use that feature you need to have all changes activated, so nothing is pending. Renaming a host is a complex precedure that will not only rename the host in WATO, but also in: <ul> <li>all rules from Host & Service Parameters</li> <li>cluster's node definitions</li> <li>a host's parent definitions</li> <li>Business Intelligence rules</li> <li>notification rules (both rule based and flexible notifications)</li> <li>internal Check_MK data like caches and performance counters</li> <li>auto-disovered services of the host</li> <li>logfile information of logwatch plugin</li> <li>stored SNMP walks</li> <li>RR databases with performance data</li> <li>RRD updates in journal of RRD Cache</li> <li>spool files of PNP4Nagios</li> <li>NagVis maps</li> <li>monitoring history entries (events and availability)</li> <li>the current monitoring state (including ackowledgements and downtimes)</li> </ul> Please note that renaming of a host involves a temporary stop of the monitoring core. This is neccessary in order to avoid situation where the old and the new name of a host is being used at the same time.

10 years, 3 months

Check_MK Werk 0918: notification: fixed exception when sending notifications as sms / ascii mail

by Andreas Boesl

ID: 0918 Title: notification: fixed exception when sending notifications as sms / ascii mail Component: Notifications Level: 2 Class: Bug Fix Version: 1.2.5i3 Flexible notification plugins with configurable parameters did not work if the parameters were configured as list of strings. This exception happened on notications send by ASCII mails and sms.

10 years, 3 months

Check_MK Werk 0162: if_brocade: New if64 Check version for Brocade VDX Switches

by Bastian Kuhn

ID: 0162 Title: if_brocade: New if64 Check version for Brocade VDX Switches Component: Checks & Agents Level: 2 Class: Incompatible Change Version: 1.2.5i3 This check does the same like the normal if64 check. The only difference is that ifName is used instead of ifDescription. You may want to do a reinventory on broace switches, because otherwise the "Check_MK Inventory" check (if used) will trigger warning state cause of unchecked services.

10 years, 3 months

Check_MK Werk 0955: zfs_arc_cache, zfs_arc_cache.l2: New Checks for Hit Ratios and Sizes of ZFS

by Bernd Stroessenreuther

ID: 0955 Title: zfs_arc_cache, zfs_arc_cache.l2: New Checks for Hit Ratios and Sizes of ZFS Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.5i3

10 years, 3 months

Check_MK Werk 0972: Do not loose site specific global settings anymore when chaning a site's configuration

by Mathias Kettner

ID: 0972 Title: Do not loose site specific global settings anymore when chaning a site's configuration Component: WATO Level: 2 Class: Bug Fix Version: 1.2.5i3 When you use distributed monitoring and have a site with site specific global settings and afterwards edited the settings of the site connections then the global settings got lost. This has now been fixed.

10 years, 3 months

Check_MK Werk 0971: Fix missing authentication of PHP addons in D-WATO when activation mode is reload

by Mathias Kettner

ID: 0971 Title: Fix missing authentication of PHP addons in D-WATO when activation mode is reload Component: WATO Level: 1 Class: Bug Fix Version: 1.2.5i3 When you set the activation mode in WATO from restart to reload and use distributed WATO then on the remote sites the hook for creating the authentication information for PHP addons like PNP4Nagios and NagVis would not be created. This has been fixed now.

10 years, 3 months

Check_MK Werk 0954: juniper_bgp_state: New Check for BGP status at Juniper Routers

by Bernd Stroessenreuther

ID: 0954 Title: juniper_bgp_state: New Check for BGP status at Juniper Routers Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.5i3

10 years, 3 months

Check_MK Werk 0917: df checks: now able to show time left until disk full as perfometer and pnpgraph

by Andreas Boesl

ID: 0917 Title: df checks: now able to show time left until disk full as perfometer and pnpgraph Component: Checks & Agents Level: 1 Class: New Feature Version: 1.2.5i3 There WATO rule <tt>Filesystems (used space and growth)</tt> now has an option where you can configure whether the time left until disk full information is always shown. If this option is set the multsite perfometer for the check is split horizontally and will additionally show the days left information. A new "Days left" pnpgraph is also available.

10 years, 3 months

Check_MK Werk 0970: liveproxyd: handle situations with more then 1024 open files

by Mathias Kettner

ID: 0970 Title: liveproxyd: handle situations with more then 1024 open files Component: Livestatus-Proxy Level: 2 Class: Bug Fix Version: 1.2.5i3 When you are using the Livestatus Proxy Daemon for connecting lots of sites and you have lots of concurrent users then two things could happen: 1. You might run out of files. The reason is that per default on most Linux systems the number of files a process is allowed to keep open is limited to 1024. The can be increased by using <tt>/etc/security/limits.conf</tt>. The script launching the <tt>liveproxyd</tt> need to issue a <tt>ulimit -S -n unlimited</tt> before starting. In the OMD builds of the Check_MK Monitoring System this has been added for recent development builds. The <tt>liveproxyd</tt> now handles this situation better and does not long run into a busy CPU loop. It waits for 5 seconds and restarts itself instead. 2. Even if you increased the number of allowed open files the <tt>liveproxyd</tt> could never open more than 1024 files on most Python versions (due to a limit of the system call <tt>select()</tt>. This has been fixed by using the <tt>poll()</tt> system call.

10 years, 3 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 May 2014