Checkmk werks level1 February 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
287 discussions

[2.3.0] Checkmk Werk 16451 created: Fix saving changes of foreign custom graphs

by Checkmk werks level 1

[//]: # (werk v2) # Fix saving changes of foreign custom graphs key | value ---------- | --- compatible | yes version | 2.3.0b1 date | 2024-02-20T09:30:44+00:00 level | 1 class | fix component | multisite edition | cee

6 months, 3 weeks

[2.3.0] Checkmk Werk 16404 created: omd cp: Fix etc/ssl/agents/legacy_ca.pem Points to Source of Copy

by Checkmk werks level 1

[//]: # (werk v2) # omd cp: Fix etc/ssl/agents/legacy_ca.pem Points to Source of Copy key | value ---------- | --- date | 2024-02-14T09:48:14+00:00 version | 2.3.0b1 class | fix edition | cre component | omd level | 1 compatible | yes Since Checkmk 2.2.0 there is a agent CA located in `etc/ssl/agents/`. This CA is different from the site CA. In particular, if updating from 2.1.0 to 2.2.0, Checkmk will create a symlink `etc/ssl/agents/legacy_ca.pem`, which points to `etc/ssl/ca.pem`. After performing an `omd cp`. This symlink would still point to the site, which was the source of the copy. The symlink is now relative. If the site was created with version 2.2.0 or above no symlink is needed.

6 months, 3 weeks

[2.3.0] Checkmk Werk 16403 created: Fix assert self._rulespec.item_name is not None

by Checkmk werks level 1

[//]: # (werk v2) # Fix assert self._rulespec.item_name is not None key | value ---------- | --- date | 2024-02-13T10:08:20+00:00 version | 2.3.0b1 class | fix edition | cre component | wato level | 1 compatible | yes A `rulespec` may have an `item_spec` without a title. In [Werk #13387](https://checkmk.com/werk/13387) changed it so that if this title is missing the the following crash occurs. ``` assert self._rulespec.item_name is not None ``` The occured if one navigates to the parameters via `Parameters for this service` and clicks `Parameters`. It is now fixed.

6 months, 3 weeks

[2.3.0] Checkmk Werk 16472 created: iLert notifications: ignore error when event is already closed

by Checkmk werks level 1

[//]: # (werk v2) # iLert notifications: ignore error when event is already closed key | value ---------- | --- date | 2024-02-07T16:05:25+00:00 version | 2.3.0b1 class | fix edition | cre component | notifications level | 1 compatible | yes When attempting to resolve an incident which was already manually resolved, an error occured. This kind of error will now be ignored.

6 months, 3 weeks

[2.3.0] Checkmk Werk 16481 created: No longer round values for Float and Percentage valuespecs

by Checkmk werks level 1

[//]: # (werk v2) # No longer round values for Float and Percentage valuespecs key | value ---------- | --- date | 2024-02-16T10:20:50+00:00 version | 2.3.0b1 class | fix edition | cre component | multisite level | 1 compatible | yes The `Float` and `Percentage` valuespecs used to round to a specified and limited number of decimal places. Now all decimal precision is displayed and used.

6 months, 3 weeks

[2.3.0] Checkmk Werk 16318 created: Connection test using SNMP credentials configured on host page

by Checkmk werks level 1

[//]: # (werk v2) # Connection test using SNMP credentials configured on host page key | value ---------- | --- compatible | yes version | 2.3.0b1 date | 2024-02-16T07:42:06+00:00 level | 1 class | fix component | wato edition | cre If you used "Save & run connection tests" on the host properties page with SNMP credentials configured, the configured password was not used for the executed tests. A workaround was to enter the password on the "Test connection" page again.

6 months, 3 weeks

[2.3.0] Checkmk Werk 16510 created: Improve InfluxDB logging

by Checkmk werks level 1

[//]: # (werk v2) # Improve InfluxDB logging key | value ---------- | --- date | 2024-02-16T09:58:19+00:00 version | 2.3.0b1 class | fix edition | cee component | core level | 1 compatible | yes The InfluxDB logger now logs the line protocol on debug level.

6 months, 3 weeks

[2.3.0] Checkmk Werk 16049 created: Render service graphs of host independent of historic metrics

by Checkmk werks level 1

[//]: # (werk v2) # Render service graphs of host independent of historic metrics key | value ---------- | --- date | 2024-02-19T07:41:52+00:00 version | 2.3.0b1 class | fix edition | cre component | multisite level | 1 compatible | yes The view "Service graphs of host" used to show the error message "No historic metrics recorded but performance data is available. Maybe performance data processing is disabled." even if the underlying single service graphs existed. This occured especially when using a host check command. The behavior is fixed to always rendering the service graphs in the view "Service graphs of host", if their performance data is available. Note that this change does not affect the same error message shown for the "Host graph" row of the "Status of Host" view, as the available performance data belongs to the services and not to the host.

6 months, 3 weeks

[2.3.0] Checkmk Werk 16520 created: Bi: creating rules should allow the old style host_labels or service_labels

by Checkmk werks level 1

[//]: # (werk v2) # Bi: creating rules should allow the old style host_labels or service_labels key | value ---------- | --- date | 2024-02-16T14:17:46+00:00 version | 2.3.0b1 class | fix edition | cre component | rest-api level | 1 compatible | yes Our host labels and service labels recently went through some major changes which included updating the REST-API fields to host_label_groups and service_label_groups. However, for reasons of backward compatibility, we decided to keep the legacy host_labels and service_labels as possible fields when creating a bi rule via the REST-API. This werk implements this change, but these legacy fields will be marked as deprecated and will not be available in our next major release. It is recommended to use the new format.

6 months, 3 weeks

[2.3.0] Checkmk Werk 16360 created: Dedicated security logging

by Checkmk werks level 1

[//]: # (werk v2) # Dedicated security logging key | value ---------- | --- date | 2024-02-16T09:38:25+00:00 version | 2.3.0b1 class | feature edition | cre component | omd level | 1 compatible | yes To make it easier to detect certain security relevant events a dedicated security log is introduced. You can find it in `var/log/security.log`. The format of each line is: 1. The date and time the logentry was created (local time) 2. The security domain and the process id. 3. The message as json with a `summary` and `details` key. The contents of the `details` vary by the domain. Currently the following domains exist: * `application_errors`: e.g if a CSRF token could not be found/validated * `auth`: e.g. successful / unsuccessful authentication attempts. (Successful authentication attempts without opening a session are currently not logged.) * `service`: e.g. the start of a site * `user_management`: e.g. change of a password Please note that this logfile is still subject to change. Additional events might be added and details may change with p-releases.

6 months, 3 weeks

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 February 2024