Checkmk werks level1 May 2020

checkmk-werks-lvl1@lists.checkmk.com

14 participants
67 discussions

Checkmk Werk 10695: Windows Agent Service will wait for Network Services

by Sergey Kipnis

ID: 10695 Title: Windows Agent Service will wait for Network Services Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 With this release Windows Agent will wait for WIndows Network availabale up to 30 seconds by default. This can prevent some rare and strange errors when plugins try to run without network. This wait period may be changed in the configuration file using yml variable system.wait_network

3 years, 11 months

Checkmk Werk 11033: Availability: Added option to change host and service state in annotations

by Ronny Bruska

ID: 11033 Title: Availability: Added option to change host and service state in annotations Component: Multisite Level: 1 Class: New feature Version: 1.7.0i1 It is now possible to set a new state for host and services in annotations.

3 years, 11 months

Checkmk Werk 10991: Cisco CPU: Fixed discovery of cisco_cpu and cisco_cpu_multiitem (updates werk #10778)

by Simon Jess

ID: 10991 Title: Cisco CPU: Fixed discovery of cisco_cpu and cisco_cpu_multiitem (updates werk #10778) Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 The Cisco CPU checks discovery ordering from Werk 7458 is revisited. There are four Cisco CPU checks: cisco_cpu, cisco_cpu_multiitem, cisco_nexus_cpu, cisco_oldcpu. We discover the Cisco CPU utilization services in the following order: - if it's a Nexus device ("NX-OS" in SysDescr and OID ".1.3.6.1.4.1.9.9.305.1.1.1.0" is set) the cisco_nexus_cpu check is used - if the device is not a Nexus device and contains the SNMP table ".1.3.6.1.4.1.9.9.109.1.1.1.1.2.*" and NOT the deprecated OID "1.3.6.1.4.1.9.9.109.1.1.1.1.5.1" (cpmCPUTotal5min) then cisco_cpu_multiitem is used. - if the device either the OID ".1.3.6.1.4.1.9.9.109.1.1.1.1.8.1" or ".1.3.6.1.4.1.9.9.109.1.1.1.1.5.1" then cisco_cpu. This acts now as a fallback and is not strict about verifying device not belonging to cisco nexus family. This as a relaxed condition to werk 5748. - if .1.3.6.1.4.1.9.2.1.57.0 exists then cisco_oldcpu is used There may be Cisco hosts which have discovered the 'wrong' check type. After a re-discovery the CPU check type may change.

3 years, 11 months

Checkmk Werk 10990: mk_logwatch: Fixed state file name if REMOTE_HOST variable contains extended IPv4 address

by Simon Jess

ID: 10990 Title: mk_logwatch: Fixed state file name if REMOTE_HOST variable contains extended IPv4 address Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 In the logwatch.cfg a cluster configuration may be of the form C:+ CLUSTER cluster-name 1.2.3.4 5.6.7.8 C:- The REMOTE_HOST variable may begin with "::ffff:HERE.COMES.IPv4.ADDRESS". In order to make this setup work correctly the mk_logwatch state file must be named as "/PATH/TO/logwatch.state.cluster-name". This has been fixed.

3 years, 11 months

Checkmk Werk 11078: Dynamic configuration: Add connector plugin API

by Lars Michelsen

ID: 11078 Title: Dynamic configuration: Add connector plugin API Component: DCD Level: 2 Class: New feature Version: 1.7.0i1 The Dynamic configuration is now loading plugins that are located below the path <tt>local/lib/check_mk/cee/dcd/plugins/connectors/</tt>. You can find a minimal example connector implementation it in your site at <tt>lib/check_mk/cee/dcd/plugins/connectors/example_connector.py</tt>. You may use this as base for your own connectors. To enable this connector, you need to copy it to the plugin directory mentioned above and uncomment the registry registration lines in the plugin (See TODO). To be able to configure connections based on this connector in the GUI, you also need to deploy a GUI plugin. An example can be found in your site at <tt>lib/check_mk/gui/cee/plugins/wato/example_dcd_connector.py</tt>. This needs to be placed in the WATO plugin directory of your site. You also need to uncomment the registry registration line in the plugin (See TODO).

3 years, 11 months

Checkmk Werk 11154: cisco_vpn_sessions: rename item "SVC" --> "AnyConnect SVC"

by Joerg Herbel

ID: 11154 Title: cisco_vpn_sessions: rename item "SVC" --> "AnyConnect SVC" Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 As a follow-up of werk #11152, this werk renames the item "SVC" of the check cisco_vpn_sessions to "AnyConnect SVC" (for clarity). Users have to re-discover the services of affected hosts for this to come into effect and potentially adjust any corresponding rules.

3 years, 11 months

Checkmk Werk 11078: Dynamic configuration: Add connector plugin API

by Lars Michelsen

3 years, 11 months

Checkmk Werk 11151: Correct handling of unsorted time periods for availability timelines

by Joerg Herbel

ID: 11151 Title: Correct handling of unsorted time periods for availability timelines Component: Livestatus Level: 1 Class: Bug fix Version: 1.7.0i1 Checkmk now handles unsorted time periods correctly when displaying availability timelines. For example, before, the time period 10:10 - 10:15, 10:00 - 10:05 would end up as 10:10 - 10:15, so checkmk dropped the second, earlier range.

3 years, 11 months

Checkmk Werk 10847: mk_oracle: Broken instance specific login in some cases

by Marcel Arentz

ID: 10847 Title: mk_oracle: Broken instance specific login in some cases Component: Checks & agents Level: 1 Class: Bug fix Version: 1.6.0p13 In some cases the SID as it is displayed on the host process list and the SID specific login data does not match if the matching is case sensitive. As a consequense the variable for the specific login has not been found, e.g. if the process is lower case but the config uses upper case SID.

3 years, 11 months

Checkmk Werk 11160: CSV/JSON/Python exports of views: improve formatting of labels

by Frans Fürst

ID: 11160 Title: CSV/JSON/Python exports of views: improve formatting of labels Component: Core & setup Level: 1 Class: Bug fix Version: 1.7.0i1 When exporting a view using %output_format=csv|json|python labels would not get exported properly (concatenated key/value pairs like "key1:value1key2:value2"). This fix turns the export for labels into raw data structures like {'key1':'value1', 'key2':'value2'}.

3 years, 11 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 May 2020