Checkmk werks level2 January 2015

checkmk-werks-lvl2@lists.checkmk.com

4 participants
17 discussions

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.

8 years, 12 months

Check_MK Werk 1927: Fixed level description in WATO rules, change from if above into at

by Mathias Kettner

ID: 1927 Title: Fixed level description in WATO rules, change from if above into at Component: WATO Level: 2 Class: Bug Fix Version: 1.2.7i1

9 years, 9 months

Check_MK Werk 1926: ps: reenable compatiblity with existing configurations

by Mathias Kettner

ID: 1926 Title: ps: reenable compatiblity with existing configurations Component: Checks & Agents Level: 2 Class: Bug Fix Version: 1.2.7i1 In werk #1563 we moved all parameters for the process check to a check parameter rule set in normal Check_MK style. Previously these parameters (like process count, CPU levels, etc.) had been set only during discovery. But that way existing configuration with rules for process inventory would not work anymore. This werk fixes this. All old inventory rule (now called discovery) work again. Also they are ediable via WATO. You can set the process parameters now in two places: during discovery and in the parameter rule. The preferred way is the new way: to set these in the parameter rule. That way changes will immediately get active without a need for a new discovery.

9 years, 9 months

Check_MK Werk 1922: Fix exception in saving of hosttags if hosttag has at least one auxiliary tag

by Mathias Kettner

ID: 1922 Title: Fix exception in saving of hosttags if hosttag has at least one auxiliary tag Component: WATO Level: 2 Class: Bug Fix Version: 1.2.7i1

9 years, 9 months

Check_MK Werk 1859: cups_queues: linux agent now runs section cups_queues in cached mode

by Goetz Golla

ID: 1859 Title: cups_queues: linux agent now runs section cups_queues in cached mode Component: Checks & Agents Level: 2 Class: Bug Fix Version: 1.2.7i1 After reports of problems with the agent run time for printer servers with very long print queues the agent now runs the cups_queues section in cached mode with a cache time of 5 mins. This means that the section is updated only every 5 mins.

9 years, 9 months

Check_MK Werk 1880: inventory_processes rules can now be configured without setting levels

by Lars Michelsen

ID: 1880 Title: inventory_processes rules can now be configured without setting levels Component: Core & Setup Level: 2 Class: Bug Fix Version: 1.2.7i1 Since werk #1563 the levels configured in the rule {inventory_processes} are not interpreted anymore. If you used this rule to configure process discovery, you can now leave the last four elements (thresholds) of. Note: If you use WATO for configuring process discovery, this change does not affect you. To configure the thresholds, you need to use the {check_parameters} option like shown in the example below: F+:etc/check_mk/main.mk # Old configuration style inventory_processes += [ ( ["sap", ], ALL_HOSTS, "SAP_ora_pmon_%s", "~ora_pmon_([A-Z][A-Z,0-9]{2,3})$", GRAB_USER, 1, 1, 1, 1 ), ] # new style configuration: inventory_processes += [ ( ["sap", ], ALL_HOSTS, "SAP_ora_pmon_%s", "~ora_pmon_([A-Z][A-Z,0-9]{2,3})$", GRAB_USER), check_parameters += [ ( {'levels' : (1, 1, 1, 1)}, ALL_HOSTS, ['proc_SAP_ora_pmon_.*'] ), ] F-:

9 years, 9 months

Check_MK Werk 1878: Fixed possible shell injection when filtering the EC archive

by Lars Michelsen

ID: 1878 Title: Fixed possible shell injection when filtering the EC archive Component: Event Console Level: 2 Class: Security Fix Version: 1.2.7i1 To optimize searches in the Event Console archive files, the event console uses "grep" to make a fast preselection of history entries. The grep command is used for different filters, like the "ID of rule". This allows normal logged in users with only GUI privileges to execute shell commands on the monitoring host with privileges of the user the Event Console is running with. Normally this is the sites user in OMD sites or the user nagios. All currently maintained versions are affected. If you are using an affected version which we offer no more releases for, you can use the patch of this Werk to fix the issue for your version. This issue has been discovered and reported by Christian Thiemann. Thanks!

9 years, 9 months

Check_MK Werk 1672: Now able reclassify logwatch messages before forwarding them to the event console

by Andreas Boesl

ID: 1672 Title: Now able reclassify logwatch messages before forwarding them to the event console Component: Event Console Level: 2 Class: New Feature Version: 1.2.7i1 You are now able to apply already existing logwatch patterns to the messages which are sent to the event console. Each message can be reclassified to a different alert level and even set to IGNORED, which causes a message not to be sent to the event console. This pre-sorting might reduce the load of the event console. Keep in mind that the logwatch pattern are configured by host and the logfile name. These restrictions do also apply to the messages intented for the event console. So you can configure a logwatch pattern specifially designed for a message from a certain logfile. For example, you can reclassify any messages from a logfile access.log containing "C Login error" to "I Login error". Any message of access.log containing the "Login error" pattern will therefore get ignored and not sent to the event console.

9 years, 9 months

Check_MK Werk 1671: windows agent: fixed gaps in eventlog monitoring after agent restart

by Andreas Boesl

ID: 1671 Title: windows agent: fixed gaps in eventlog monitoring after agent restart Component: Checks & Agents Level: 2 Class: Bug Fix Version: 1.2.7i1 The windows eventlog monitoring was not entirely continuous. After the agent started it determined determined the initial record number for each eventlog. Per default the start number was the last record. Thus resulted in monitoring gaps as long as the windows was not running, e.g. windows startup. With this fix, the windows agent now uses a statefile (<tt>eventstate.txt</tt>) which contains the last processed eventrecord ids for each eventlog. On startup the statefile is read and the record numbers are set accordingly.

9 years, 9 months

Check_MK Werk 1850: netscaler_health.fan, netscaler_health.psus, netscaler_health.temp: new checks to monitor the health of Citrix Netscaler Loadbalancers

by Goetz Golla

ID: 1850 Title: netscaler_health.fan, netscaler_health.psus, netscaler_health.temp: new checks to monitor the health of Citrix Netscaler Loadbalancers Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.7i1

9 years, 9 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level2 January 2015