ID: 3990
Title: now uses xml instead of lxml. now able to query counters smaller chunks. now only queries relevant sections
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.4.0i2
Now uses xml instead of lxml. Unfortunaly lxml is not available in all distributions, so
we had to switch back to xml which is considerably slower in parsing xml messages.
You can try to install the python module lxml with the command "pip install lxml".
Now able to query counters smaller chunks. There were some bigger netapp clusters which
raised an out of memory error while answering the call. The reason was that the answer grew
too big. We now query smaller chunks and merge them together.
Now only queries relevant sections. Right at the beginning, the agent queries the available
licenses on the system and skips sections, which's licenses are specifically not enabled.
This feature is currently only implemented for a few section and will possibly improved later on.
ID: 3651
Title: Fixed potential segfault with Nagios core when accessing log/commands table via Livestatus.
Component: Livestatus
Level: 2
Class: Bug Fix
Version: 1.4.0i3
Under rare circumstances, the Nagios core could crash when the "log" or
"commands" table was queried via Livestatus. Sites using the Micro Core
were not affected by this bug.
ID: 3979
Title: vbox_guest: Only try to fetch VBox state in case the vboxguest module is loaded
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.4.0i2
ID: 3939
Title: f5_bigip_conns: readded performance data and graphs
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.4.0i2
f5_bigip_conns check was missing perfdata and graphs since werk #3692. This has been fixed now.
ID: 3989
Title: Logwatch patterns: now able to change state of context lines
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.4.0i2
You can now reclassify the state of context lines to a different state.
For example to IGNORE, which prevents that the line is forwarded to the event console.
ID: 4042
Title: Fix missing From address in synchronous SMTP notifications
Component: Notifications
Level: 1
Class: Bug Fix
Version: 1.4.0i2
If you use the new synchronous STMP devlivery for emails and do
not specify an explicity From address, then the From address
would be empty. This has been fixed.