Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
16031 discussions

Checkmk Werk 11165: Windows agent service can be set in mode delayed auto start

by Lars Michelsen

ID: 11165 Title: Windows agent service can be set in mode delayed auto start Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 Any Windows service can be marked as <tt>Automatic (Delayed Start)</tt>. This mode means short wait for other Windows services marked as <tt>Automatic</tt>. The delayed mode may help to have network services ready when the service starts, for example. With this release Checkmk Windows Agent supports this mode. <tt>Automatic (Delayed Start)</tt> mode may be enabled using either config file or WATO.

4 years, 4 months

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

by Lars Michelsen

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.

4 years, 4 months

Checkmk Werk 11081: Agent signing is now executed in background job

by Lars Michelsen

ID: 11081 Title: Agent signing is now executed in background job Component: agents Level: 1 Class: Bug fix Version: 1.7.0i1 Signing agents in a large Agent Bakery installation can take a long time. Therefore, the signing process is now performed in a background job, just like the baking of agent packages.

4 years, 4 months

Checkmk Werk 11034: sap_hana_ess: Fixed permanent crit state of started threads

by Ronny Bruska

ID: 11034 Title: sap_hana_ess: Fixed permanent crit state of started threads Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 The check was always in CRIT state because of the section 'Started threads". This has been fixed.

4 years, 4 months

Checkmk Werk 11166: Windows service waits for network service during start

by Sergey Kipnis

ID: 11166 Title: Windows service waits for network service during start Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 During the start Windows Agent service waits for network up to 30 seconds. This may help to prevent strange errors if some plugins require network services available. Value 30 second is default and may be changed in config file using parameter <tt>system.wait_network</tt>

4 years, 4 months

Checkmk Werk 11165: Windows agent service can be set in mode delayed auto start

by Sergey Kipnis

4 years, 4 months

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

4 years, 4 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.

4 years, 4 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.

4 years, 4 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.

4 years, 4 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1