Checkmk werks level1 April 2023

checkmk-werks-lvl1@lists.checkmk.com

23 participants
118 discussions

Checkmk Werk 15598: group_config: deleting a non-existing group no longer has a 400 response

by Gav

ID: 15598 Title: group_config: deleting a non-existing group no longer has a 400 response Component: REST API Level: 1 Class: Bug fix Version: 2.3.0b1 This werk introduces a fix to the contact_group, host_group and service_group endpoints. Previously when deleting an object or bulk deleting a list of objects, the rest-api would respond with a 400 status code when the group didn't exist. We now respond with a 404 Not Found.

1 year, 5 months

Checkmk Werk 15263: netscaler_tcp_conns: Improve metric display

by Rebekka Seltmann

ID: 15263 Title: netscaler_tcp_conns: Improve metric display Component: Checks & agents Level: 1 Class: Bug fix Version: 2.3.0b1 Previously the server and client connection metrics of the check "netscaler_tcp_conns" were displayed in scientific notation, as well as having a non-userfriendly title. This has been corrected in this werk.

1 year, 5 months

Checkmk Werk 15602: mk-job: Cleanup after execution was interrupted

by Solomon Jacobs

ID: 15602 Title: mk-job: Cleanup after execution was interrupted Component: Checks & agents Level: 1 Class: Bug fix Version: 2.3.0b1 Previously, if the wrapper program <tt>mk-job</tt> was interrupted by a reboot, the <tt>Job</tt> service would continue to show the job, which was started by <tt>mk-job</tt>. This job was shown to be running despite it being terminated by the reboot. This can be fixed by removing the corresponding file created by <tt>mk-job</tt>. With this werk, <tt>mk-job</tt> cleans up the file after being interrupted. Thus, these terminated jobs will no longer be shown as running.

1 year, 5 months

Checkmk Werk 15529: hyperv_vms: Transform failed during cmk-update-config

by Moritz Kiemer

ID: 15529 Title: hyperv_vms: Transform failed during cmk-update-config Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0b3 Discovered services of the plugin <tt>hyperv_vms</tt> would result in error messages during update. The displayed message was: Transform failed: host='heute', plugin='hyperv_vms', ruleset='hyperv_vms', params={'state': ...}, error=MKUserError(None, 'Found no matching alternative.') You can safely ignore this message. With this werk the message will no longer appear.

1 year, 5 months

Checkmk Werk 15415: Interface checks: Fix errors in perfometer rendering

by Joerg Herbel

ID: 15415 Title: Interface checks: Fix errors in perfometer rendering Component: Checks & agents Level: 1 Class: Bug fix Version: 2.3.0b1 This issue only affected network interface services. After discovering new services or after an update, the user interface initially displayed `Exception: list index out of range` in the place where the perfometer is supposed to be displayed. The log file var/log/web.log also recorded these errors: C+: 2023-04-11 10:00:28,884 [40] [cmk.web 78582] error rendering performeter Traceback (most recent call last): ... IndexError: list index out of range C-: These errors quickly disappeared after a couple of check cycles. As of this werk, these error messages are not displayed anymore. Instead, the perfometer is rendered as soon as all necessary metrics are found.

1 year, 5 months

Checkmk Werk 15528: logwatch_ec: Invalid parameters issue during discovery and update config

by Moritz Kiemer

ID: 15528 Title: logwatch_ec: Invalid parameters issue during discovery and update config Component: Checks & agents Level: 1 Class: Bug fix Version: 2.1.0p26 The WATO ruleset of the logwatch EC forwarding performed a too strict validation. This led to errors during update config and the service discovery, if corresponding services where discovered. Update config would report <tt>Transform failed: host='myHost', plugin='logwatch_ec', ruleset='logwatch_ec', params={'expected_logfiles': [...']}, error=MKUserError(None, 'Found no matching alternative.')</tt> while the parameters column of the disocvery page reports "Invalid check parameter". With this werk those messages disappear - until then they can safely be ignored.

1 year, 5 months

Checkmk Werk 15460: agent_azure: Fix an error when collecting metrics for Express Route vNet Gateway

by Sofia Colakovic

ID: 15460 Title: agent_azure: Fix an error when collecting metrics for Express Route vNet Gateway Component: agents Level: 1 Class: Bug fix Version: 2.3.0b1 Previously, the Azure agent would show an error when collecting metrics for the Express Route vNet Gateway: C+: cmk.special_agents.agent_azure.ApiError: Failed to find metric configuration for provider: Microsoft.Network, resource Type: virtualNetworkGateways, metric: P2SConnectionCount, Valid metrics: ExpressRouteGatewayPacketsPerSecond, ExpressRouteGatewayBitsPerSecond, ... C-: The VNet Gateway service wasn't affected by this. Now, the error gets handled by the Azure agent plugin.

1 year, 5 months

Checkmk Werk 15651: user_config: setting connector when creating user with no authentication

by Wontek Hong

ID: 15651 Title: user_config: setting connector when creating user with no authentication Component: REST API Level: 1 Class: Bug fix Version: 2.3.0b1 Prior to this werk, the connector type was not set to htpasswd when creating an user with no authentication. This created the user but subsequently prevented the user from being edited on the interface. This werk fixes this issue by setting the connector per default.

1 year, 5 months

Checkmk Werk 15557: Resolve indexed IP for ICMP Echo Request

by Timotheus Bachinger

ID: 15557 Title: Resolve indexed IP for ICMP Echo Request Component: Checks & agents Level: 1 Class: Bug fix Version: 2.0.0p35 If you're using the active check <tt>check_icmp</tt> (ICMP Echo Requests) in combination with <tt>Ping IPv4/6 address identified by its index</tt>, the plugin crashed with: C+: (3, u'check_icmp: Failed to resolve $: Name or service not known') C-: This is fixed now.

1 year, 5 months

Checkmk Werk 15461: azure_agent_info: Stop suppressing Graph client errors

by Sofia Colakovic

ID: 15461 Title: azure_agent_info: Stop suppressing Graph client errors Component: Checks & agents Level: 1 Class: Bug fix Version: 2.3.0b1 With the werk 14533 we started suppressing Graph client errors. This was needed in the version 2.1 because Graph client errors couldn't be avoided in case the app used to call the Azure API didn't have the "Directory.Read.All" Graph permission. These errors can now be avoided by un-selecting "Users in the Active Directory", "AD Connect Sync" and "App Registrations" services in the agent configuration, which makes error suppression no longer necessary.

1 year, 5 months

← Newer
1
...
6
7
8
9
10
11
12
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 April 2023