Checkmk werks level1 November 2023

checkmk-werks-lvl1@lists.checkmk.com

1 participants
219 discussions

[2.3.0] Checkmk Werk 15307 adapted: logwatch_ec: tcp remote forwarding: create one spool file per service

by Checkmk werks level 1

Werk 15307 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: logwatch_ec: tcp remote forwarding: create one spool file per service Class: fix Compatible: compat Component: checks Date: 1699863833 Edition: cre Knowledge: doc Level: 1 Version: 2.3.0b1 This Werk affects you if you have a logwatch_ec check which forwards events to a remote syslog hosts and if you activated the option "Create a separate check for each logfile". In this case all separate services shared one spoolfile. This lead to the problem, that one event in the spoolfile was displayed as one event for each separate service (but it was only sent out once, when the remote was reachable again). In some conditions events might been unnoticeable dropped, because the spoolfile was overwritten by another logwatch service. Now each logwatch service will have their own spoolfile. The spoolfiles will be automatically assigned to their logwatch service. After all your logwatch_ec services sent all their spoolfiles out, you may manually consult the following folder for <tt>spoolfile.*</tt> files: <tt>./var/check_mk/logwatch_spool/<hostname></tt> If there are any spoolfiles in this folder, they could not be assigned to a logwatch service. If you still want them to be forwarded, move them to one of the folders, otherwise they can be deleted. <tt>./var/check_mk/logwatch_spool/<hostname>/item_<url_encode(item)></tt> ------------------------------------<diff>------------------------------------------- Title: logwatch_ec: tcp remote forwarding: create one spool file per service Class: fix Compatible: compat Component: checks Date: 1699863833 Edition: cre Knowledge: doc Level: 1 - Version: 2.2.0p15 ? ^ ^ - + Version: 2.3.0b1 ? ^ ^ This Werk affects you if you have a logwatch_ec check which forwards events to a remote syslog hosts and if you activated the option "Create a separate check for each logfile". In this case all separate services shared one spoolfile. This lead to the problem, that one event in the spoolfile was displayed as one event for each separate service (but it was only sent out once, when the remote was reachable again). In some conditions events might been unnoticeable dropped, because the spoolfile was overwritten by another logwatch service. Now each logwatch service will have their own spoolfile. The spoolfiles will be automatically assigned to their logwatch service. After all your logwatch_ec services sent all their spoolfiles out, you may manually consult the following folder for <tt>spoolfile.*</tt> files: <tt>./var/check_mk/logwatch_spool/<hostname></tt> If there are any spoolfiles in this folder, they could not be assigned to a logwatch service. If you still want them to be forwarded, move them to one of the folders, otherwise they can be deleted. <tt>./var/check_mk/logwatch_spool/<hostname>/item_<url_encode(item)></tt>

11 months, 3 weeks

[2.3.0] Checkmk Werk 16191 adapted: Activate changes: Performance improvement in CME

by Checkmk werks level 1

Werk 16191 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Activate changes: Performance improvement in CME Class: feature Compatible: compat Component: checks Date: 1698068521 Edition: cme Level: 1 Version: 2.3.0b1 The preparation phase for distributing changes to remote sites typically takes longer in a managed edition to ensure that each customer is handled separately. This phase has been accelerated with additional caching and improved storage of intermediate results. ------------------------------------<diff>------------------------------------------- Title: Activate changes: Performance improvement in CME Class: feature Compatible: compat Component: checks Date: 1698068521 Edition: cme Level: 1 Version: 2.3.0b1 The preparation phase for distributing changes to remote sites typically takes longer in a managed edition to ensure that each customer is handled separately. - This phase has been accelerated with additional caching. + This phase has been accelerated with additional caching and improved storage of intermediate results.

11 months, 3 weeks

[2.3.0] Checkmk Werk 16191 created: Activate changes: Performance improvement in CME

by Checkmk werks level 1

Title: Activate changes: Performance improvement in CME Class: feature Compatible: compat Component: checks Date: 1698068521 Edition: cme Level: 1 Version: 2.3.0b1 The preparation phase for distributing changes to remote sites typically takes longer in a managed edition to ensure that each customer is handled separately. This phase has been accelerated with additional caching.

11 months, 3 weeks

[2.3.0] Checkmk Werk 16279 deleted: service_discovery: redirect response header incorrectly configured to an absolute URI

by Checkmk werks level 1

Werk 16279 was deleted. The following Werk is no longer relevant. Title: service_discovery: redirect response header incorrectly configured to an absolute URI Class: fix Compatible: compat Component: rest-api Date: 1700141008 Edition: cre Level: 1 Version: 2.3.0b1 When calling the service discovery endpoint, the redirect response header 'location' was set to an absolute URI, when it should be a relative URI. This werk addresses this issue by setting the URI correctly in the redirect responses.

11 months, 3 weeks

[2.2.0] Checkmk Werk 15307 created: logwatch_ec: tcp remote forwarding: create one spool file per service

by Checkmk werks level 1

Title: logwatch_ec: tcp remote forwarding: create one spool file per service Class: fix Compatible: compat Component: checks Date: 1699863833 Edition: cre Knowledge: doc Level: 1 Version: 2.2.0p15 This Werk affects you if you have a logwatch_ec check which forwards events to a remote syslog hosts and if you activated the option "Create a separate check for each logfile". In this case all separate services shared one spoolfile. This lead to the problem, that one event in the spoolfile was displayed as one event for each separate service (but it was only sent out once, when the remote was reachable again). In some conditions events might been unnoticeable dropped, because the spoolfile was overwritten by another logwatch service. Now each logwatch service will have their own spoolfile. The spoolfiles will be automatically assigned to their logwatch service. After all your logwatch_ec services sent all their spoolfiles out, you may manually consult the following folder for <tt>spoolfile.*</tt> files: <tt>./var/check_mk/logwatch_spool/<hostname></tt> If there are any spoolfiles in this folder, they could not be assigned to a logwatch service. If you still want them to be forwarded, move them to one of the folders, otherwise they can be deleted. <tt>./var/check_mk/logwatch_spool/<hostname>/item_<url_encode(item)></tt>

11 months, 3 weeks

[2.3.0] Checkmk Werk 15303 created: logwatch_ec: remove spool files after reading them

by Checkmk werks level 1

Title: logwatch_ec: remove spool files after reading them Class: fix Compatible: compat Component: checks Date: 1698764921 Edition: cre Level: 1 Version: 2.3.0b1 Before this fix spool files were only removed when they were too old or if there were too many of them. Spool files that got deleted after reading will be recreated if there was an error while sending a message.

11 months, 3 weeks

[2.3.0] Checkmk Werk 16279 created: service_discovery: redirect response header incorrectly configured to an absolute URI

by Checkmk werks level 1

Title: service_discovery: redirect response header incorrectly configured to an absolute URI Class: fix Compatible: compat Component: rest-api Date: 1700141008 Edition: cre Level: 1 Version: 2.3.0b1 When calling the service discovery endpoint, the redirect response header 'location' was set to an absolute URI, when it should be a relative URI. This werk addresses this issue by setting the URI correctly in the redirect responses.

11 months, 3 weeks

[2.1.0] Checkmk Werk 15307 adapted: logwatch_ec: tcp remote forwarding: create one spool file per service

by Checkmk werks level 1

Werk 15307 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: logwatch_ec: tcp remote forwarding: create one spool file per service Class: fix Compatible: compat Component: checks Date: 1699863833 Edition: cre Knowledge: doc Level: 1 Version: 2.1.0p37 This Werk affects you if you have a logwatch_ec check which forwards events to a remote syslog hosts and if you activated the option "Create a separate check for each logfile". In this case all separate services shared one spoolfile. This lead to the problem, that one event in the spoolfile was displayed as one event for each separate service (but it was only sent out once, when the remote was reachable again). In some conditions events might been unnoticeable dropped, because the spoolfile was overwritten by another logwatch service. Now each logwatch service will have their own spoolfile. The spoolfiles will be automatically assigned to their logwatch service. After all your logwatch_ec services sent all their spoolfiles out, you may manually consult the following folder for <tt>spoolfile.*</tt> files: <tt>./var/check_mk/logwatch_spool/<hostname></tt> If there are any spoolfiles in this folder, they could not be assigned to a logwatch service. If you still want them to be forwarded, move them to one of the folders, otherwise they can be deleted. <tt>./var/check_mk/logwatch_spool/<hostname>/item_<url_encode(item)></tt> ------------------------------------<diff>------------------------------------------- Title: logwatch_ec: tcp remote forwarding: create one spool file per service Class: fix Compatible: compat Component: checks Date: 1699863833 Edition: cre Knowledge: doc Level: 1 Version: 2.1.0p37 This Werk affects you if you have a logwatch_ec check which forwards events to a remote syslog hosts and if you activated the option "Create a separate check for each logfile". In this case all separate services shared one spoolfile. This lead to the problem, that one event in the spoolfile was displayed as one event for each separate service (but it was only sent out once, when the remote was reachable again). In some conditions events might been unnoticeable dropped, because the spoolfile was overwritten by another logwatch service. Now each logwatch service will have their own spoolfile. The spoolfiles will be automatically assigned to their logwatch service. After all your logwatch_ec services sent all their spoolfiles out, you may manually consult the following folder for <tt>spoolfile.*</tt> files: <tt>./var/check_mk/logwatch_spool/<hostname></tt> If there are any spoolfiles in this folder, they could not be assigned to a logwatch service. If you still want them to be forwarded, move them to one of - the hash folders, otherwise they can be deleted. ? ----- + the folders, otherwise they can be deleted. - <tt>./var/check_mk/logwatch_spool/<hostname>/<<sha1_hash_of_item></tt> ? ^ ^^^^ ^^^^^ ^^ + <tt>./var/check_mk/logwatch_spool/<hostname>/item_<url_encode(item)></tt> ? ^^^^^ ^^^ ^^^ ^^^ +

11 months, 3 weeks

[2.1.0] Checkmk Werk 15976 created: mssql_backup: Correct timezone difference for last backup date

by Checkmk werks level 1

Title: mssql_backup: Correct timezone difference for last backup date Class: fix Compatible: compat Component: checks Date: 1696949130 Edition: cre Knowledge: doc Level: 1 State: unknown Version: 2.1.0p37 This werk is relevant for users monitoring the age of the last backup time of mssql databases in different timezones. The date/time of the last backup of a mssql database is currently stored in local host time without the information about the host timezone. When this time is used to check the age of the last backup, it is interpreted in the Checkmk server timezone. When using different timezones, this leads to incorrect values for "Age of last database backup" and if the age is negative, in newer Checkmk versions to the warning "Cannot reasonably calculate time since last backup (hosts time running ahead)". The mssql agent plugin will now store the time in UTC and the mssql_backup check will interpret the time accordingly. You will need to update the agent plugin mssql.vbs to receive the corrected times.

11 months, 3 weeks

[2.1.0] Checkmk Werk 16294 created: ibm_imm_temp: Fix <tt>ValueError (could not convert string to float: '')</tt>

by Checkmk werks level 1

Title: ibm_imm_temp: Fix <tt>ValueError (could not convert string to float: '')</tt> Class: fix Compatible: compat Component: checks Date: 1700149060 Edition: cre Knowledge: undoc Level: 1 State: unknown Version: 2.1.0p37 This werk fixes the crash mentioned above.

11 months, 3 weeks

← Newer
1
...
8
9
10
11
12
13
14
...
22
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 November 2023