ID: 2645
Title: Fix garbled notification context when \n appears in service description
Component: Notifications
Level: 2
Class: Bug Fix
Version: 1.2.7i3
When your service has the name <tt>C:\tmp\network.log</tt>, then the <tt>\n</tt> would
be interpreted as newline and everything after the \ was lost. This has been fixed.
ID: 2617
Title: Improved error handling in case of agent error but piggyback data available
Component: Core & Setup
Level: 1
Class: Bug Fix
Version: 1.2.7i3
ID: 2653
Title: winperf_msx_queues: fixed incorrect cancelation of check claiming no counters were available
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.7i3
In versions 1.2.6p11 and 1.2.6p12 this check would report unknown state with the message "no
counters available, transport service running?" even though there were counters
ID: 2635
Title: pandacom_psu, pandacom_fan, pandacom_sys_temp, pandacom_10gm_temp, pandacom_fc_temp: new checks for Pandacom SpeedCarrier Chassis 5u
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i3
These checks monitor the power supply and fan states, the system temperature and the FC and 10GM modules
temperature of a Pandacom SpeedCarrier Chassis 5u.
ID: 2616
Title: LDAP: Improved handling of multiple connections (Name conflicts, cross directory sync)
Component: Multisite
Level: 1
Class: New Feature
Version: 1.2.7i3
Since Check_MK can synchronize with multiple LDAP directories at the same time, new situations
could occur which Check_MK did not handle properly for all cases yet.
For example it is possible that name conflicts (user id) occur between LDAP connections when
different LDAP directories have equal named users. Previous versions did synchronize the user
using the first connection to be synchronized (take a look at the configuration to check the
connection order) and silently skipped equal named users from other directories.
This version intruces so called "LDAP connection suffixes" to solve this situation. This suffix
is used identify name conflicting users between directories. You can use whatever you like as
suffix, but for better identification it is recommended to use the official domain name as suffix.
For example "corp.de" if you domain is identified like this.
The connection suffix is appended to the user id for all user accounts having name conflicts during
the synchronisation.
Additionally, when a user tries to log in with his regular user name, for example <tt>hh</tt>, but
the login is refused due to the name conflict, he can add the domain suffix to his username, e.g.
<tt>hh(a)corp.de</tt> to tell Check_MK which directory he is associated to.
Addionionally, it is now possible to configure the role and group sync plugins to gather group
memberships for the users of a connection from another one. This might be needed when you have
multiple LDAP directories somehow connected (Active Directory forest) where the users belong
to one LDAP directory and the groups are found in another LDAP directory. Now, when these
groups have members of the other LDAP directory, these memberships could not be synchronized
to Check_MK in previous versions. This is now possible to be configured. But the default is
to gather the group memberships of users from the connection they are associated with.
ID: 2432
Title: Forwarded notifications are now visible within the rule based notifications analysis
Component: Notifications
Level: 1
Class: New Feature
Version: 1.2.7i3
The context of forwarded notifications was not stored for debug purposes on the notification receiver.
Therefore forwarded notifications were never shown in the analysis page of the master site.
ID: 2431
Title: WATO Snapshots: Fixed broken performancedata backup
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.7i3
WATO was unable to import snapshots with included performance data.
This error was a side effect of werk #2486.