ID: 5455
Title: solaris_services: New check which monitors single services of Solaris systems
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.5.0i2
ID: 5496
Title: lnx_if: fix an issue that could lead to a crash of the agent if no interface address is returned
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i3
ID: 5723
Title: Fixed broken sorting of services
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.5.0i3
The sorting was a case insentivitve text sorting at least since
1.4.0p7. This has now been fixed to work like as case insensitive
sort with the addition that texts and numbers are separated from
eachother before sorting.
ID: 5722
Title: View/dashboard list: Show link to view only for not hidden and published views
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.5.0i3
ID: 5725
Title: Fixed changing view filter default values not being effective right after editing
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.4.0p25
When editing the default values of filters in views (or dashboards) and saving the view,
the default filter variables were not effective in all cases in the view rendered after
edit. When closing and opening the view again the filter options were set as configured.
ID: 5724
Title: View/Dashboard list: Link titles only for views/dashboards visible to the user
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.5.0i3
Previously also overriden views/dashboards were linked.
ID: 5764
Title: df.include: Fixed dynamic levels in ruleset 'Filesystem (used space and growth)'
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i3
When configuring dynamic levels, eg. for filesystems, if you configure
the dynamic levels for example like this:
larger than 100GB: 90% WARN / 95% CRIT
larger than 1TB: 95% WARN / 98% CRIT
This will result in all filesystems smaller than 100GB in always being OK.
If you also want to set levels for all filesystems smaller than 100GB
then you have to choose 0 bytes, eg.
larger than 0B: 85% WARN / 90% CRIT
With werk 2725 this was not allowed any more. Fixed that.
ID: 5702
Title: Allow spaces in Windows eventlog name
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.5.0i3
Add support for Windows eventlogs whose names contain spaces. Previously, such
eventlog names could not be handled as the first space-separated word was
interpreted to be the complete name.