ID: 5619
Title: memory.include: Ignoring levels led to a crash because the handling of the paramters was not correct
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i3
ID: 5270
Title: Improved Agent Updater Check behaviour
Component: agents
Level: 1
Class: New feature
Version: 1.5.0i3
Formerly, the Agent Updater Check did not update immediately after a manual action on the host. This could lead to some confusion.
Notably, you had to wait for the next update cycle to have a successful Agent registration displayed within the Check.
In order to mitigate this situation, the Agent Updater now:
- Invalidates the cache file age after registration in order to have an Update executed with next Check_MK Agent execution
- Updates the cachefile information after a successful manual update.
The latter action is not performed in --debug option mode.
Information about the cachefile updates will be displayed in -vv mode
ID: 5689
Title: Newline in mrpe include file crashed Windows agent
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i3
A newline character in a file included through the mrpe configuration
option <tt>include</tt> (see Werk #266) put Windows agent into an
eternal loop.
ID: 5651
Title: Fixed agent TCP connect timeout being used for whole communication (1.5.0i2 regression)
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.5.0i3
The configurable "Agent TCP connect timeout" was used not only for the connect phase of
the TCP connection. This lead to many timeout messages like "agent:myhost:12.16.11.42: timed out".
ID: 5613
Title: Auxiliary tags: New column 'Tags using this auxiliary tag' shows related tag group
Component: Multisite
Level: 1
Class: New feature
Version: 1.5.0i3
ID: 5447
Title: fjdarye500_ca_ports: New checks monitor IO and throughput of Fujitsu storage CA ports
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.5.0i2
By default CA ports in mode 'CA' and 'CARA' are discovered.
Moreover port indices can be configured in the related
discovery rule 'Discovery of Fujtsu storage CA ports'.
There are no hints in the SNMP data which ports are active
thus the above rule may be useful.
ID: 5486
Title: Add permission for admins to see custom views, dashboards and reports
Component: Multisite
Level: 1
Class: New feature
Version: 1.5.0i3
Previously, admins could only see custom views, dashboards and reports of a
user if the owner set the option "Make this view/dashboard/report available for
other users". Now admins can see the views, dashboards and reports of all
users. This also implies that admins are allowed to edit and clone these views.
ID: 5618
Title: skype.sip_stack: Fixed "missing key" error which caused a check crash
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i3
Above error was a result of different key notations for
the same object, eg. in "skype.sip_stack" we got
- "SIP - Incoming Responses Dropped /Sec" and
- "SIP - Incoming Responses Dropped/sec"
Now we normalize these keys by ignoring upper/lower
case and spaces.
ID: 5688
Title: Windows agent: numerous fixes to only_from
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i3
The setting only_from was handled improperly in many ways:
* The IPv4 loopback address 127.0.0.1 did not always work in
only_from, depending on what kind of client was used on localhost.
Now if the IPv4 loopback address is given in only_from, the
corresponding IPv6 loopback ::1 is added there to ensure the correct
functionality with different clients on localhost.
* IPv6 addresses converted from only_from IPv4 addresses were not
output in section Check_MK. This was a regression from 1.2.8
introduced in the huge refactoring
c5ee818358e695b01c2f2dbc05ad0713723a37f8.
* IPv6 addresses were output incorrectly in section Check_MK:
* the last colon-separated group was always missing.
* the groups were output as decimal instead of hexadecimal digits.
* the groups were output in network byte order instead of host byte
order, leading to incorrect output.