ID: 8582
Title: Fix hint for how rule sets are interpreted for four rule sets. Were invalid type 'list'
Component: WATO
Level: 1
Class: Bug fix
Version: 1.4.0i1
ID: 8583
Title: Make "Export as PDF" honor graph time range when specified via display option (small computer icon)
Component: Reporting & Availability
Level: 1
Class: Bug fix
Version: 1.4.0i1
ID: 8576
Title: Fixed segfaults in cmc when Stats{And,Or,Negate} was used for EC tables
Component: Livestatus
Level: 1
Class: Bug fix
Version: 1.4.0i3
Livestatus queries caused a segfault when Stats: lines were combined with
operators when querying eventconsole tables.
ID: 8577
Title: Fixed Livestatus queries for custom_variable_names columns.
Component: cmc
Level: 1
Class: Bug fix
Version: 1.4.0i3
Previously, Livestatus queries for custom_variable_names columns had to
prepend an underscore to a variable name to find a given variable. This was
an implementation detail which should not shine through, and it was highly
inconsistent with the handling of custom_variables columns. This has been
fixed, so no spurious underscore is needed anymore.
ID: 8578
Title: Fixed C-style mangling of performance variable names in Graphite/InfluxDB connections
Component: cmc
Level: 1
Class: Bug fix
Version: 1.4.0i3
Previously, the performance variable names were not mangled in a reversible
manner, even when C-style mangling was requested.
ID: 8579
Title: Generalize Livestatus filter operators
Component: Livestatus
Level: 1
Class: New feature
Version: 1.4.0i3
Previously, some filter operator did not work for numbers or had only a special
meaning with certain columns. This has been generalized in a uniform way, so all
operators work for numbers now, too.
The operators <tt>~</tt>, <tt>=~</tt>, and <tt>~~</tt> interpret numbers as bit
sets, and have the following meaning:
<ul>
<li><tt>x ~ y</tt> means: <tt>x</tt> is a superset of <tt>y</tt></li>
<li><tt>x =~ y</tt> means: <tt>x</tt> is a subset of <tt>y</tt></li>
<li><tt>x ~~ y</tt> means: <tt>x</tt> contains at least one element of <tt>y</tt></li>
</ul>
This is consistent with the way attribute list columns work and makes the
Livestatus semantics more regular.
ID: 8580
Title: Removed space leaks related to dynamic columns.
Component: Livestatus
Level: 1
Class: Bug fix
Version: 1.4.0i3
When some special columns were queried via Livestatus, the monitoring core
leaked memory. This affected the following columns:
<ul>
<li><tt>mk_logwatch_file</tt> in table <tt>hosts</tt></li>
<li><tt>value</tt> in table <tt>eventconsolereplication</tt></li>
<li><tt>rrddata</tt> in tables <tt>hosts</tt> and <tt>services</tt></li>
</ul>
ID: 8572
Title: Made scheduling of check helpers more robust
Component: cmc
Level: 2
Class: Bug fix
Version: 1.4.0i1
Under very rare circumstances the monitoring core miscounted the number of
idle helpers, leading to an endless loop with 100% CPU load.
ID: 8573
Title: Handle large regular expressions more gracefully
Component: cmc
Level: 1
Class: Bug fix
Version: 1.4.0i2
Livestatus queries with large regular expressions in their filters could
lead to a stack overflow and consequently to a termination of the micro
core. To handle this in a more robust way, we set a limit on the size and
complexity of a regular expression, and bump the stack sizes of the
Livestatus threads from 64kB to 256kB. The net result is that we can
correctly handle regular expression patters of up to roughly 2k characters,
the exact value depends on the regex features used. For larger expressions
we return a failure status in a clean way.