ID: 1013
Title: Sort host names naturally, e.g. foobar11 comes after foobar2
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.5i5
Hostnames are now sorted naturally. That means that sequences of numbers
are being interpreted as numbers. This also works for host names that
have the form of an IPv4 address, e.g. <tt>10.1.1.5</tt> is now correctly
sorted before <tt>10.1.1.11</tt> and <tt>srv17_3</tt> comes before <tt>src17_108</tt>.
This new sorting is implemented in the status GUI and also in WATO.
ID: 0167
Title: mk_inventory.linux: Changed field separator from pipe to tab
Component: HW/SW-Inventory
Level: 1
Class: Bug Fix
Version: 1.2.5i5
Some rpm packages using the pipe symbol as part of her description. Cause of this reason we need another internal separator.
ID: 0168
Title: f5_bigip_pool: Added Wato configuration
Component: WATO
Level: 1
Class: New Feature
Version: 1.2.5i5
Thresholds for the minimum number of left pool members can now be definied using WATO.
ID: 0995
Title: raritan_pdu_outletcount: new check for outlet count of Raritan PX-2000 family PDUs
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.5i5
ID: 1012
Title: Fix quoting of \ in custom checks with nagios core
Component: Core & Setup
Level: 2
Class: Incompatible Change
Version: 1.2.5i5
When you are using Nagios as montitoring core then backslashes contained
in <tt>custom_checks</tt> (Classical active and passive Nagios checks) would
be interpreted by Nagios. That way single backslashes would usually vanish
und you would have to duplicate them.
The Check_MK Micro Core never interpreted these backslashes so it was
transparent for the user.
This fix changes the behaviour of Check_MK in a way that also with the
Nagios core you need only one backslash. Backslashes are transparent
now.
<b>NOTE</b>: If you have custom checks that contain backslashes (for
example as part of names or passwords) then you need to remove
duplicate backslashes after this update!
ID: 0944
Title: oracle_tablespaces: fixed calculation of space left and number of remaining increments
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.5i5
The remaining increments and space left was not correctly calculated when the
remaining memory space was not a multiple of the increment size.<br>
For example:<br>
C+:
Tablespace
900 MB used
100 MB free space for autoincrement
200 MB increment size
C-:
The previous version calculated 900 MB as maximum size, because the increment size was greater
than the remaining autoincrement space. This was wrong. The last increment also uses the remaining
space, even if the remaining size is smaller than the increment size.<br><br>
As a result, this fix actually increases the amount of available free space,
so it should not have any negative side effects for already configured limits.
ID: 0943
Title: if.include: fixed incorrect traffic percentage values in the check output of if checks
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.5i5
There was a display bug in the traffic percentages. The value was off by factor 8.<br>
This bug didn't cause wrong check results or performance data values, just a visual glitch.