Checkmk werks level1 February 2022

checkmk-werks-lvl1@lists.checkmk.com

21 participants
74 discussions

Checkmk Werk 13600: Custom Windows agent port was not respected during update

by Sergey Kipnis

ID: 13600 Title: Custom Windows agent port was not respected during update Component: Checks & agents Level: 2 Class: Bug fix Version: 2.1.0i1 Previously, during <tt>update</tt> Windows agent always opened default port, 6556, in the firewall, even if the TCP port had been changed by WATO With this release the problem had been eliminated.

2 years, 7 months

Checkmk Werk 13613: Admin can edit report schedules for reports not published to them

by Óscar Nájera

ID: 13613 Title: Admin can edit report schedules for reports not published to them Component: Reporting & Availability Level: 1 Class: Bug fix Version: 2.1.0i1 Users with permission "Manage all scheduled reports", usually admins, can edit scheduled reports. However, due to werk 12991, if the report itself is not published for the user doing the edit, he will not find it and he will be unable to edit it. This werk fixes that incompatibility as the admin user can edit the report and its schedule. Still compatible with werk 12991, if the report is not published to the user, he will not be able to schedule that report for himself. He would first need to clone the report, or edit the report to publish it to other users, both of which he can do as an admin.

2 years, 7 months

Checkmk Werk 13711: Service discovery with non-ASCII service names

by Joerg Herbel

ID: 13711 Title: Service discovery with non-ASCII service names Component: Setup Level: 1 Class: Bug fix Version: 2.1.0i1 The service discovery in the GUI was not able to handle certain non-ASCII characters in service names (non-ASCII characters with Unicode code points larger than 255). Such characters were by mistake replaced by other characaters. As a result, affected services were continously displayed as unmonitored, even after adding them to the list of monitored services. Note that this issue did not affect the service discovery via the command line (<tt>cmk -I</tt> / <tt>cmk -II</tt>).

2 years, 7 months

Checkmk Werk 13573: Reenable ntopng flows page

by Timotheus Bachinger

ID: 13573 Title: Reenable ntopng flows page Component: ntopng_integration Level: 1 Class: Bug fix Version: 2.1.0i1 This is a regression after introducing the vlan awareness: the ntopng flows were not displayed anymore. This is fixed now.

2 years, 7 months

Checkmk Werk 13572: Disable SSL checking with ntop

by Timotheus Bachinger

ID: 13572 Title: Disable SSL checking with ntop Component: ntopng_integration Level: 1 Class: Bug fix Version: 2.1.0i1 Disabling the checking of SSL certificate torwards a ntopng instance was broken since 2.0.0p13. This is fixed now.

2 years, 7 months

Checkmk Werk 13391: Remove support for IE 11

by Kenneth Okoh

ID: 13391 Title: Remove support for IE 11 Component: Multisite Level: 1 Class: New feature Version: 2.1.0i1

2 years, 7 months

Checkmk Werk 13561: agent_kubernetes: deprecate special agent and associated checks

by Lisa Pichler

ID: 13561 Title: agent_kubernetes: deprecate special agent and associated checks Component: Checks & agents Level: 1 Class: New feature Version: 2.1.0i1 As of Checkmk version 2.1.0, the special agent "agent_kubernetes" is deprecated and will be removed in Checkmk version 2.2.0. This also affects the associated checks and inventory plugins:<br> <br> <ul> <li>k8s_assigned_pods</li> <li>k8s_component_statuses</li> <li>k8s_conditions</li> <li>k8s_daemon_pod_containers</li> <li>k8s_daemon_pods</li> <li>k8s_endpoint_info</li> <li>k8s_ingress_infos</li> <li>k8s_job_container</li> <li>k8s_job_info</li> <li>k8s_namespaces</li> <li>k8s_nodes</li> <li>k8s_persistent_volume_claims</li> <li>k8s_persistent_volumes</li> <li>k8s_pod_container</li> <li>k8s_replicas</li> <li>k8s_resources (including pods, cpu and memory)</li> <li>k8s_roles</li> <li>k8s_service_port</li> <li>k8s_stateful_set_replicas</li> <li>k8s_stats_fs</li> <li>k8s_stats_network</li> <li>k8s_storage_classes</li> </ul> <br> The special agent and checks continue to function in Checkmk version 2.1.0. Please refer to the user guide for detailed instructions on how to set up the new special agent for Kubernetes.

2 years, 7 months

Checkmk Werk 13405: Allow to disable thread levels

by Benedikt Seidl

ID: 13405 Title: Allow to disable thread levels Component: Checks & agents Level: 1 Class: Bug fix Version: 2.1.0i1 The rule "Number of threads" can set both relative and absolute levels for the number of threads. Up until this Werk it was not possible to remove said levels completely once they where set. Now this is possible. For example you can define a base rule matching all hosts to check for absolute levels and add another rule matching a single host removing the absolute levels from the base rule and only check for relative levels. To accomplish that choose "No levels" for the absolute levels on the single host.

2 years, 7 months

Checkmk Werk 13634: REST API: Creating hosts via API does not trigger agent baking by default anymore

by Lars Michelsen

ID: 13634 Title: REST API: Creating hosts via API does not trigger agent baking by default anymore Component: REST API Level: 1 Class: Bug fix Version: 2.1.0i1 The REST API endpoints for creating hosts (Create a host, Create a cluster host, Bulk create hosts) were triggering and agent baking job for the new hosts after configuring the hosts. This may be useful in some cases, but in the most cases it is not intended to do it. Since the job needs some resources for the baking and also holds locks during baking, the job might slow down subsequent API calls. To address both needs we now added an optional query parameter <tt>?bake_agent=[1|0]</tt> to the API calls mentioned above. The default behaviour has been changed: If you don't specify the parameter, the agents are not baked anymore. Only when you call the endpoints with <tt>?bake_agent=1</tt>, the agent baking job will be started.

2 years, 7 months

Checkmk Werk 13530: FIX node and cluster data source consistency validation

by Simon Jess

ID: 13530 Title: FIX node and cluster data source consistency validation Component: Setup Level: 1 Class: Bug fix Version: 2.1.0i1 While creating a cluster the configured data sources are checked against each node. If they are not the same the cluster cannot be saved. Previously only the tags IDs {{agent}} or {{snmp}} were checked. If for example a node has the data source {{Checkmk agent}} then the cluster must have the same datasource. Otherwise the error {{The node NODENAME has datasources and 'agent' while the cluster has datasources and 'no-agent'.}} was display. Now auxilary tags are also involved which may be set through other tags or tag groups, eg. the tag {{cmk-agent}} implicilty sets the auxilary tag {{tcp}}. This auxilary tag may also be set through custom tags or tag groups. Details: The tags {{cmk-agent}}, {{all-agents}} and {{special-agents}} contain the auxilary tag {{tcp}} and belong to the default tag group {{agent}}. During validation the exact values {{all-agents}} and {{special-agents}} are checked and after these {{tcp}} is taken into account. This behaviour is equivalent to the decision which data sources are added to a host. Regarding the tag group {{snmp_ds}} the validation checks the tag values {{snmp-v1}}, {{snmp-v2}} and the auxilary tag {{snmp}}.

2 years, 7 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 February 2022