ID: 13599
Title: Windows event log: Add filtering of sequential duplicate messages
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.1.0i1
Only identical consecutive messages will be filtered.
As soon as a different message comes in between, the filter will be reset.
Example:
Without filtering
W Dec 14 14:32:56 0.10016 SOURCE Message_Itself
W Dec 14 14:33:57 0.10016 SOURCE Message_Itself
W Dec 14 14:34:58 0.10016 SOURCE Message_Itself
W Dec 14 14:35:59 0.10016 SOURCE Message_Again
With filtering
W Dec 14 14:32:56 0.10016 SOURCE Message_Itself
[the above message was repeated 2 times]
W Dec 14 14:35:59 0.10016 SOURCE Message_Again
ID: 13197
Title: Add space as valid URL character
Component: Setup
Level: 1
Class: Bug fix
Version: 2.0.0p19
With Werk 13195 a stricter URL validation was introduced. In the original
implementation the space character was not allowed. Unfortunately servicenames
with spaces are not encoded properly and spaces used to work. Since this is
also common behaviour and does not impose security risks the space is allowed
again.
ID: 13454
Title: agent_smb_share: Special agent for Windows SMB share
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.1.0i1
SMB share special agent can be configured by creating a rule in
Setup > Agents > Other integrations. Multiple shared folders can
be configured for a host along with patterns that match files
to be monitored.
Monitored files are discovered as fileinfo or fileinfo_groups
services.
ID: 13598
Title: Windows agent flag sendall is correctly defined now
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
Previously WATO used invalid flag name <tt>send_all</tt>.
Thus making impossible to set the flag using WATO.
With this release WATO uses correct flag name
<tt>sendall</tt>.
ID: 13656
Title: Fix already used error using host and service label conditions
Component: Setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
If you used label conditions in rules and the same key was used for host and
service labels, the error "Only one value per KEY can be used at a time.foo:bar
is already used." ocurred. From now on, each label type will be validated
seperatly.
ID: 13287
Title: Views/Dashboards/Reports are now rendered faster in setups with a large number of users
Component: Multisite
Level: 1
Class: New feature
Version: 2.1.0i1
The loading time of customized views, dashboards and reports no longer increases with the number of configured users.
Due to various (unsuccessful) attempts to load customized elements for users, a monitoring system with 2000 users
could introduce an additional rendering latency of ~200ms on every page.
ID: 13482
Title: Systemd unit 'check_mk_agent-async' waits for network.target
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
Sometimes after a reboot the asynchronous Checkmk agent systemd service
will immediately try to contact the server in order to download (or look
for) an agent update.
To avoid spamming the system log, we wait for the network target to be up.
ID: 13515
Title: Fix possible LockNotOwnedError if data is queried from redis
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
If a query to redis took to long, the following error could occur in
~/var/log/web.log:
"redis.exceptions.LockNotOwnedError: Cannot release a lock that's no longer
owned".
This could have happened if you e.g. filtered for host labels in a view.
ID: 13607
Title: Successful configuration updates now produce a change
Component: Multisite
Level: 1
Class: New feature
Version: 2.1.0i1
Checkmk now adds a change after a successful configuration update with
cmk-update-config. cmk-update-config is e.g. executed during a Checkmk
version update. The change ensures that configuration changes are pushed
to remote sites after an update. If any errors occur during an update
no change is added.
ID: 13523
Title: Validate configured rules when updating configuration
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The Checkmk update procedure (<tt>cmk-update-config</tt>) now validates all configured rules
and logs "ERROR: Invalid rule configuration detected" in case of an error. If you encounter
such errors, your configuration contains rules that need to be corrected. We recommend to open
the affected rules in the GUI. Upon attempting to save them, any problematic field will be
highlighted.
Invalid rule values can for example originate from invalid regular expressions, which were
unfortunately still allowed in Python 2 but are forbidden in Python 3, see also
https://checkmk.com/de/werk/11974.