Checkmk werks level1 September 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
218 discussions

[2.3.0] Checkmk Werk 16997 deleted: NagVis: Updated to 1.9.43

by Checkmk werks level 1

Werk 16997 was deleted. The following Werk is no longer relevant. [//]: # (werk v2) # NagVis: Updated to 1.9.43 key | value ---------- | --- date | 2024-08-30T07:45:48+00:00 version | 2.3.0p15 class | fix edition | cre component | packages level | 1 compatible | yes

2 months

[2.3.0] Checkmk Werk 16869 created: azure: Don't fetch vNet gateway peerings from another subscription

by Checkmk werks level 1

[//]: # (werk v2) # azure: Don't fetch vNet gateway peerings from another subscription key | value ---------- | --- date | 2024-09-06T15:15:56+00:00 version | 2.3.0p15 class | fix edition | cre component | checks level | 1 compatible | yes Previously, the Azure agent would crash when monitoring vNet gateways which have peerings from a different subscription. The agent wouldn't report the crash and the consequence was that the affected vNet gateway wasn't monitored. Now, the agent will not monitor vNet gateways peerings from another subscription.

2 months

[2.3.0] Checkmk Werk 16868 created: azure: Fetch metrics in bulk

by Checkmk werks level 1

[//]: # (werk v2) # azure: Fetch metrics in bulk key | value ---------- | --- date | 2024-09-06T15:03:25+00:00 version | 2.3.0p15 class | fix edition | cre component | checks level | 1 compatible | yes Until now, Azure agent fetched metrics for each resource individually. This resulted in many requests made to the Azure API. After the changes in Azure API rate limits it started causing agent timeouts in large environments. Now, the Azure agent fetches metrics in bulk per resource type and region. This way the number of requests is significantly reduced. Since metrics are no longer fetched per resource, parallel execution is also removed together with the `Force agent to run in single thread` option.

2 months

[2.4.0] Checkmk Werk 14236 created: Fixed missing hosts on remote sites

by Checkmk werks level 1

[//]: # (werk v2) # Fixed missing hosts on remote sites key | value ---------- | --- date | 2024-09-09T07:25:03+00:00 version | 2.4.0b1 class | fix edition | cme component | wato level | 1 compatible | yes If a folder belonging to a customer contained hosts from several sites of the same customer, there was a risk that these hosts were not monitored at all.

2 months

[2.0.0] Checkmk Werk 10471 adapted: mk_logwatch: Add option to limit context

by Checkmk werks level 1

Werk 10471 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: mk_logwatch: Add option to limit context Class: feature Compatible: compat Component: checks Date: 1573027255 Edition: cre Knowledge: undoc Level: 1 Version: 2.0.0i1 If the plugin mk_logwatch is configured to send context along with found messages, the amount of data can become quite large. This werk adds the option of limiting the context given for every warning or critical message to a given number of lines befor and after the message. For instance, to limit the context to 3 lines before and four lines after the message, set the option "maxcontextlines=3,4". This option can be configured using the WATO rule "Text logfiles". ------------------------------------<diff>------------------------------------------- Title: mk_logwatch: Add option to limit context Class: feature Compatible: compat Component: checks Date: 1573027255 Edition: cre Knowledge: undoc Level: 1 Version: 2.0.0i1 If the plugin mk_logwatch is configured to send context along with found messages, the amount of data can become quite large. This werk adds the option of limiting the context given for every warning or critical message to a given number of lines befor and after the message. For instance, to limit the context to 3 lines before - and four lines after the message, set the option "limitcontext=3,4". ? -- ^^ + and four lines after the message, set the option "maxcontextlines=3,4". ? ^^ +++++ This option can be configured using the WATO rule "Text logfiles".

2 months

[2.2.0] Checkmk Werk 17265 created: Git: Support long commit messages

by Checkmk werks level 1

Title: Git: Support long commit messages Class: fix Compatible: compat Component: wato Date: 1725272831 Edition: cre Level: 1 Version: 2.2.0p33 When the Git integration was enabled, creating thousands of hosts could result in a crash. This was caused by a limit of the command line. This werk improves the Git integration to support longer messages.

2 months

[2.0.0] Checkmk Werk 10471 adapted: mk_logwatch: Add option to limit context

by Checkmk werks level 1

2 months

[2.3.0] Checkmk Werk 17265 created: Git: Support long commit messages

by Checkmk werks level 1

[//]: # (werk v2) # Git: Support long commit messages key | value ---------- | --- date | 2024-09-02T10:27:11+00:00 version | 2.3.0p16 class | fix edition | cre component | wato level | 1 compatible | yes When the Git integration was enabled, creating thousands of hosts could result in a crash. This was caused by a limit of the command line. This werk improves the Git integration to support longer messages.

2 months

[2.0.0] Checkmk Werk 10471 adapted: mk_logwatch: Add option to limit context

by Checkmk werks level 1

2 months

[2.4.0] Checkmk Werk 17265 created: Git: Support long commit messages

by Checkmk werks level 1

[//]: # (werk v2) # Git: Support long commit messages key | value ---------- | --- date | 2024-09-02T10:27:11+00:00 version | 2.4.0b1 class | fix edition | cre component | wato level | 1 compatible | yes When the Git integration was enabled, creating thousands of hosts could result in a crash. This was caused by a limit of the command line. This werk improves the Git integration to support longer messages.

2 months

← Newer
1
...
14
15
16
17
18
19
20
21
22
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 September 2024