Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15936 discussions

[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.

7 months, 1 week

[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.

7 months, 1 week

[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.

7 months, 1 week

[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.

7 months, 1 week

[2.3.0] Checkmk Werk 16519 created: Bi: creating rules should allow the same host/service label group format as the response

by Checkmk werks level 1

[//]: # (werk v2) # Bi: creating rules should allow the same host/service label group format as the response key | value ---------- | --- date | 2024-02-16T13:37:01+00:00 version | 2.3.0b1 class | fix edition | cre component | rest-api level | 1 compatible | yes This werk makes it possible to create a BI rule via the REST-API using the same schema that is returned in a response. Previously, this was not possible after some changes to how our label_groups are now configured.

7 months, 1 week

[2.3.0] Checkmk Werk 16393 created: notification_rule: allow custom plugin names when selecting cancel without a restart

by Checkmk werks level 1

[//]: # (werk v2) # notification_rule: allow custom plugin names when selecting cancel without a restart key | value ---------- | --- date | 2024-02-14T13:46:22+00:00 version | 2.3.0b1 class | fix edition | cre component | rest-api level | 1 compatible | yes We recently made a change that would allow you to create a notification rule, via the REST-API using a custom plugin but also setting the option "cancel_previous_notifications". However, an apache restart was required since we were verifying the custom plugin via the runtime generated schema. This werk fixes this issue by removing this verification from the schema and checking at the endpoint.

7 months, 1 week

[2.3.0] Checkmk Werk 16392 created: global_settings: LSI MegaRAID: Logical Disks selected by default

by Checkmk werks level 1

[//]: # (werk v2) # global_settings: LSI MegaRAID: Logical Disks selected by default key | value ---------- | --- date | 2024-02-13T15:13:19+00:00 version | 2.3.0b1 class | fix edition | cre component | wato level | 1 compatible | yes

7 months, 1 week

[2.3.0] Checkmk Werk 16405 created: cmk-update-config: Don't Read Characters Pressed before Prompt Appears

by Checkmk werks level 1

[//]: # (werk v2) # cmk-update-config: Don't Read Characters Pressed before Prompt Appears key | value ---------- | --- date | 2024-02-14T14:29:36+00:00 version | 2.3.0b1 class | fix edition | cre component | omd level | 1 compatible | yes During `cmk-update-config` can prompt you with questions about how to continue the update. This is an example. ``` Exception while trying to load rulesets: You can abort the update process (A) and try to fix the incompatibilities or try to continue the update (c). Abort update? [A/c] ``` Previously, these prompts would read input, which was typed before the prompt was shown. Now, only the input is read after the prompt is shown.

7 months, 1 week

[2.3.0] Checkmk Werk 16084 created: Baked agents: Show full hash in Check_MK Agent service

by Checkmk werks level 1

[//]: # (werk v2) # Baked agents: Show full hash in Check_MK Agent service key | value ---------- | --- date | 2024-02-15T08:39:14+00:00 version | 2.3.0b1 class | fix edition | cee component | agents level | 1 compatible | yes As an addition to Werk #15424, the *Check_MK Agent* service now also shows the full 16-digit agent hash at the service details.

7 months, 1 week

[2.3.0] Checkmk Werk 16368 created: service_discovery: Fixed internal server error on service discovery when IP cannot be resolved

by Checkmk werks level 1

[//]: # (werk v2) # service_discovery: Fixed internal server error on service discovery when IP cannot be resolved key | value ---------- | --- date | 2024-02-12T12:34:21+00:00 version | 2.3.0b1 class | fix edition | cre component | rest-api level | 1 compatible | yes Prior to this Werk, when a service discovery was requested from a host whose IP could not be resolved, the endpoint returned a 500 error status (Internal Server Error). This Werk corrects this behavior and now returns error code 400.

7 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1