Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
16034 discussions

Checkmk Werk 11391: Redis agent plugin now supports databases listening on unix sockets

by Óscar Nájera

ID: 11391 Title: Redis agent plugin now supports databases listening on unix sockets Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 The Redis agent plugin is extendend to support instances listening on unix sockets. They must be explicitly declared on the configuration file, auto-detect feature of the agent does not work in this case. An example of how to define an instance use the socket file as a HOST and then port must be labled unix-socket. F+:/etc/check_mk/mk_redis.cfg REDIS_INSTANCES=(MY_socket_Redis) REDIS_HOST_MY_socket_Redis="/var/redis/redis.sock" REDIS_PORT_MY_socket_Redis="unix-socket" F-:

4 years, 1 month

Checkmk Werk 11365: vms_if: Fix broken discovery and check execution

by Joerg Herbel

ID: 11365 Title: vms_if: Fix broken discovery and check execution Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 A bug in the check <tt>vms_if</tt>, which monitors network interfaces on OpenVMS, prevented the corresponding services from being discovered and resulted in a crash for already discovered services (error message: "TypeError: '<' not supported between instances of 'str' and 'int'"). This bug occurred since 2012 and affects all hosts. With this werk, <tt>vms_if</tt> will again be discovered and work.

4 years, 1 month

Checkmk Werk 11207: Separate service for ESX snapshot summaries

by Frans Fürst

ID: 11207 Title: Separate service for ESX snapshot summaries Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 Requesting a VM snapshot summary for the vCenter or each ESX host would lead to multiply reported VM snapshots if the respective VM had been configured as host in Checkmk, too. This change moves the summary information to a new service called "ESX Snapshot Summary"

4 years, 1 month

Checkmk Werk 11343: ServiceNow: Make rule more flexible

by Timotheus Bachinger

ID: 11343 Title: ServiceNow: Make rule more flexible Component: Notifications Level: 1 Class: New feature Version: 1.7.0i1 The enterprise notification plugin "ServiceNow" has a new rule option for setting the incident state in case of an incoming recovery. Furthermore all rules for changing the incident state can be configured by using an Integer as state. This can be useful in case the default mapping was changed by the user in ServiceNow and does not fit anymore the mapping definied in checkmk.

4 years, 1 month

Checkmk Werk 11326: drdb: fixed invalid check parameters at discovery stage

by Lisa Pichler

ID: 11326 Title: drdb: fixed invalid check parameters at discovery stage Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 When initiating the discovery for the DRDB check, the parameter 'diskstates_inventory' is reported as an unidentified key. This has been fixed.

4 years, 1 month

Checkmk Werk 11470: Fixed site context filter used in views

by Ronny Bruska

ID: 11470 Title: Fixed site context filter used in views Component: Multisite Level: 1 Class: Bug fix Version: 1.7.0i1 If you configured a site filter in a multisite view, the filter had no effect when calling the view. The cause was that the url variables for the site where not present at runtime. >From now on the site filter variables are taken from the context of each view.

4 years, 1 month

Checkmk Werk 11277: Fix wrong allocation of colorant for printer supplies

by Jonas Kluger

ID: 11277 Title: Fix wrong allocation of colorant for printer supplies Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 For some printers the mapping of the colorant did not match to the description of the service. This mappings can vary depending on the manufacturer. The generic mapping was replaced by using the correct link between description and colorant. Before this fix and depending on the manufacturer the service description could have been wrong. The result was a discrepancies between the service color name and the perf-o-meter color. If your printer has such a difference, please make sure to rediscover your host services.

4 years, 1 month

Checkmk Werk 11268: mssql.vbs: Add SQL Server Native Client provider 11 (SQLNCLI11)

by Simon Jess

ID: 11268 Title: mssql.vbs: Add SQL Server Native Client provider 11 (SQLNCLI11) Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 The legacy connection provider {{SQLOLEDB}} does not support {{TLSv1.2}}. The new {{OLE DB}} driver, {{MSOLEDBSQL}}, includes the support for the latest {{TLS 1.2}} standards and is backwards compatible with SQL Server Native Client 11 ({{SQLNCLI11}}).

4 years, 1 month

Checkmk Werk 11267: if_fortigate: Use ifName as ifAlias

by Simon Jess

ID: 11267 Title: if_fortigate: Use ifName as ifAlias Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 The original check plugin {{if_fortigate}} uses the {{ifName}} under the guise of {{ifAlias}} because on Fortigate devices the {{ifName}} contains the technical interface names. By contrast {{ifDescr}} or {{ifAlias}} may contain user defined names. In the ruleset {{Network Interface and Switch Port Discovery}} under {{Appearance of network interface}} the item can be specified: Either use the {{Use index}}, {{Use description}} or {{Use alias}}. With the incompatible werk 6638 the {{ifName}} was substituted with {{ifAlias}}. This means that the technical interface names are not available any more. This werk reverts the check plugin back to its original state: use {{ifName}} as {{ifAlias}} in order to make these technical names available again. We cannot simply add another SNMP field because this may cause unforeseen performance loss. In the future we have to find a performant solution to make the following four SNMP fields available for item names: {{ifIndex}}, {{ifName}}, {{ifDescr}} and {{ifAlias}}. Thus if you have configure {{Use alias}} in the ruleset {{Network Interface and Switch Port Discovery}} under {{Appearance of network interface}} on Fortigate devices you have to rediscover these hosts.

4 years, 1 month

Checkmk Werk 11471: Fixed default LDAP synchronization setting of central sites

by Ronny Bruska

ID: 11471 Title: Fixed default LDAP synchronization setting of central sites Component: Multisite Level: 1 Class: Bug fix Version: 1.7.0i1 The default setting for "Sync with LDAP connections" in the connection settings of central sites showed "Disabled user synchronization (use master site users)". If you saved this page, because of changes in other settings, this default setting was set for the site in question, leading to missing synchronizations on that site. >From now on the default for central sites is "Sync users with all connections" as stated in the inline help.

4 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1