ID: 12026
Title: Performance Graph Dashlets: Specify by Graph Title instead of by Index
Component: Setup
Level: 1
Class: New feature
Version: 2.1.0i1
The graph displayed by a performance graph dashlet is now specified
by selecting from a list of available graphs, represented by their
titles. This list can optionally be pre-filtered by host name or service
description. Before this werk, graphs in performance graph dashlets were
specified by a number indexing the graphs produced by the corresponding
service (n'th graph).
Performance graph dashlets created before this werk will continue to
work. However, upon editing them the next time, you will have to re-
select the graph to be displayed.
ID: 12073
Title: Fix exception on editing users if rulebased notifications are disabled
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
If rulebased notifications were not used, editing a user resulted in an error
"(invalid notification period None)".
ID: 12135
Title: More detailed audit logging
Component: Setup
Level: 2
Class: New feature
Version: 2.1.0i1
With Checkmk 2.0 the audit logging of the setup has been extended to be more
detailed. We added the general capability of tracking changes to configuration
objects on attribute level.
The audit log can be opened going to "Setup > General > Audit log". On that
page you have the list of recorded changes with the new "Details" column. You
also have the general filter form that can be used for filtering the changes
you are interested in.
You can also find context related links from hosts, users and rules to the audit
log entries that are specific to this object.
You may notice that the "Details" column is empty for a lot of changes.
This is because we need to turn on the recording of details specific to each
action. In Checkmk, we have implemented this for the most common actions first.
These are:
<ul>
<li>Create, edit and delete hosts</li>
<li>Create, edit and delete folders</li>
<li>Service discovery (bulk and single host discovery)</li>
<li>Create, edit and delete users</li>
<li>Create, edit, move and delete rules</li>
</ul>
Over time, we will increase the level of detail of the other existing log messages.
ID: 11975
Title: Validate regexes in BI rules during config update
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.1.0i1
Unfortunately Python 2 allowed to enter invalid regexes into arguments of BI rules.
In Python 3 these values will lead to a crash when evaluating the service condition.
E.g. a argument like "C:\Users\" leads to the error message "re.error: incomplete escape \U at position 2".
Therefore the Checkmk update procedure (cmk-update-config) validates the regular expressions in BI rules and
logs "ERROR: Invalid regular expression in BI rule detected" if the regex cannot be evaluated.
If you encounter these errors your configuration probably contains rules that needs to be corrected.
Previous Checkmk versions were not complaining about those rules but they were not able to match.
You should change these rules according to https://docs.checkmk.com/latest/en/regexes.html prior to the update
of your production site.
E.g. you should change windows paths like "C:\Users\" to "C:\\Users\\" with double backslashes.
ID: 12072
Title: Fix show mode always displaying show more
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
This fixes a regression since werk #12058.
ID: 11906
Title: Improve message length computation in fetcher protocol
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
The computation of the length of SNMP payloads is now consistent
with improperly escaped JSON strings.
Previously, the inconsistency could result in the crash
of the SNMP checks.
ID: 12060
Title: Use new filter search form on all pages with tables
Component: Multisite
Level: 1
Class: New feature
Version: 2.1.0i1
To stay consistent, the new filter search form was added to all pages
containing tables. Pages with already included filter options, e.g. views, were
excluded.
The search can be found in the page menu bar and replaces the old inpage
search, placed in the table actions.
ID: 12134
Title: Fix dynamic configuration executing only phase 1 in some cases
Component: Dynamic host configuration
Level: 1
Class: Bug fix
Version: 2.1.0i1
When a dcd connection was configured to operate in the central site of
a distributed setup, the connection could fail with only executing
the phase 1 of the synchronization. This was caused by a file
<tt>etc/check_mk/dcd.d/wato/distributed.mk</tt> in the central site
telling the DCD that it was a remote site.
ID: 11954
Title: AWS limits: missing titles display as "???" in service monitoring rules
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
Some of the rules for AWS limits in the service monitoring rulesets did not
display properly: they showed "???" instead of proper titles. This has been
fixed. Affected rulesets are: Glacier Limits, S3 Limits, EC2 Limits, ELB
Limits, ELBv2 Limits, EBS Limits, RDS Limits.
ID: 11450
Title: BI compiliation: fixed incorrect host regex pattern matching
Component: BI
Level: 1
Class: Bug fix
Version: 2.1.0i1
The host regex pattern matcher missed the implicit $ character at the end of each configured pattern.
This led to more hosts being found.