Title: align quoting of synchronous and asynchronous MRPE
Class: fix
Compatible: incomp
Component: checks
Date: 1700489068
Edition: cre
Level: 1
Version: 2.3.0b1
You are affected by this change if you use asynchronous MRPE and used double
quotes (<tt>"</tt>) in the MRPE command.
Quoting of mrpe commands differed between cached and non cached mrpe checks.
With this Werk the quoting rules for the normal/synchronous execution of MRPE
are applied to asynchronous MRPE commands.
The following can now be applied to both asynchronous and normal/synchronous
execution of MRPE commands: Use single quotes on the first level of quoting.
This command will correctly show <tt>output with spaces</tt> in the Service
output:
<tt>bash -c 'echo "output with spaces"'</tt>
If you execute asynchronous MRPE and the command uses double quotes on the
first level of quoting, adapt it accordingly.
Title: Fix "Metric history" context filter on view edit
Class: fix
Compatible: compat
Component: multisite
Date: 1700552738
Edition: cee
Level: 1
Version: 2.3.0b1
If you edited a view with the context filter "Metric history", the value was
always "Only first 10 sorted results", even if another value was set before.
This was just a problem with the default choice of the dropdown. If you used
the view, the filter should have been worked as expected.
Title: Protect automation user secret against timing attacks
Class: security
Compatible: compat
Component: wato
Date: 1700216645
Edition: cre
Level: 1
Version: 2.3.0b1
This Werks improves how the secret of an automation user is validated during login.
Prior to the Werk, the automation user's password was not checked in a way that is safe against (theoretical) timing attacks.
This is fixed now.
Even though this Werk improves security, it does not address an exploitable vulnerability.
To aid automated scanning we assign a CVSS score of 0.0 (None) (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N).
Title: oracle_crs_res: TypeError: Resource.__init__() got an unexpected keyword argument 'enabled'
Class: fix
Compatible: compat
Component: checks
Date: 1700145397
Edition: cre
Level: 1
Version: 2.3.0b1
Agent output changed with newer oracle databases, it now includes "enabled"
data. Previous version of this check could not handle this and crashed with
the following error:
<tt>TypeError: Resource.<strong>init</strong>() got an unexpected keyword argument 'enabled'</tt>
oracle_crs_res now ignores all additional data.
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>
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.
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.
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.
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>
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.