ID: 5732
Title: BI aggregations are now customer aware
Component: WATO
Level: 2
Class: New feature
Version: 1.5.0i3
The configuration if the BI aggregations is now handled in a customer aware
way by the Check_MK Managed Services Edition. You can now configure each
aggregation to be associated with a customer, the provider or being globally
available. The aggregations are assigned to the provider by default.
In case you want to have an aggregation only be synchronized to a single
customer, you can configure it in the aggregation properties.
A customer only get's the BI packs and BI rules synchronized that are
needed to handle the aggregations that are made available to this customer.
ID: 5731
Title: Custom icons and actions: Add new macro $USER_ID$
Component: Multisite
Level: 1
Class: New feature
Version: 1.5.0i3
The macro <tt>$USER_ID</tt> has been added to the replacement mechanic of
"Custom icons and actions" URL. This macro is replaced with the ID of the
user that is currently working with the GUI.
ID: 5671
Title: Use RE2 regular expression engine for Livestatus queries.
Component: Livestatus
Level: 2
Class: New feature
Version: 1.5.0i3
Livestatus offers various places where a regular expression can be used, e.g. in
its "Filter:" header for GET queries. The previous implementation had various
problems, which have all been fixed by switching to a new regular expression
engine (RE2, see https://github.com/google/re2):
<ul>
<li>Unicode was not handled correctly: RE2 fully understands UTF-8, so this has
been fixed.</li>
<li>Unbounded memory usage during matching: This could lead to stack overflows
and CMC/Nagios crashes when trying to match some classes of regular expressions
on long inputs. RE2 guarantees that this won't happen, it either complains that
a regular expression is too complicated (which is hard to provoke) or runs in
constant memory afterwards.</li>
<li>Exponential runtime: Some classes of regular expressions could lead to
exponential runtime, blocking Livestatus threads and using CPU time for some
millenia or more. RE2's runtime is linear in the size of the regular expression
and the input, so this has been fixed, too.</li>
</ul>
As an additional bonus, most of the time RE2 is quite a bit faster than the
previous implementation.
RE2's regular expression syntax (https://github.com/google/re2/wiki/Syntax) is
basically a superset of the previous POSIX extended regular expression syntax
(http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag…),
so you won't have to change your patterns.
Note that one esoteric detail is different, though, namely the semantics of
submatching (see https://swtch.com/~rsc/regexp/regexp2.html#posix). If you
relied on this, you probably already had some problems, because almost every
POSIX regex implementation out there was buggy in some way (see
https://wiki.haskell.org/Regex_Posix#Results_and_Bugs).
ID: 5670
Title: Handle history files from older EC versions, which have fewer columns.
Component: Event Console
Level: 1
Class: Bug fix
Version: 1.5.0i3
History files written by older versions of the EC might contain fewer
columns than a newer EC handles. This fix fills these missing columns with
their default values, avoiding log messages like
unknown precedence '' in table eventconsolehistory
in cmc.log later.
ID: 5730
Title: Graph export can now use custom consolidation function
Component: metrics
Level: 1
Class: New feature
Version: 1.5.0i3
In addition to werk #8643 it is now possible to provide the optional key
<tt>consolidation_function</tt> to control which consolidation function
should be used when calculating aggregated numbers.
Possible values are:
<ul>
<li><tt>"consolidation_function": "max"</tt> - The default</li>
<li><tt>"consolidation_function": "min"</tt></li>
<li><tt>"consolidation_function": "average"</tt></li>
</ul>
ID: 5272
Title: Make Real-Timer-Helper Pool configurable
Component: Core & setup
Level: 1
Class: New feature
Version: 1.5.0i3
The number of Maximum concurrent Real-Time checks is now configurable.
You can change the setting on the GUI at Global Settings - Monitoring Core.
Default value is set to 1, which preserves the previous behavior.
ID: 5271
Title: Better handling of erroneous deployment information in Agent Bakery
Component: agents
Level: 1
Class: Bug fix
Version: 1.5.0i3
Depending of the state of the agent deployment information file for a host, the pages "Automatic agent updates" and "Agent update status" would crash and show only partial information.
This is now mitigated by handling corrupt agent deployment files per-host and displaying an error message in a convenient format and location on the affected pages.
ID: 5729
Title: Fixed loosing configured icons when editing bookmark lists
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.5.0i3
When editing the bookmark list and an input error is shown to the
user, for example when a title is empty, all previously configured
icons were reset. They are kept now.