ID: 2341
Title: LDAP Sync: Automatically syncing credential changes to slave sites in distributed setups
Component: Multisite
Level: 1
Class: New Feature
Version: 1.2.7i2
When using the LDAP sync while having a distributed setup users might not be able to access
the GUI on the slave sites when their password was changed in LDAP. This could only be
fixed by an admin which performed a manual WATO synchronisation of the current configuration.
This has now been changed. When the password change has been detected, the master site tries
to synchronize the profile of the user to the configured and reachable remote site(s). If
this fails, the site is marked as "to be synchronized". Then the admin can perform the sync
manually once the site is available again.
ID: 2235
Title: lnx_quota: Extended linux quota check with group quota check
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i2
Extended linux quota check with group quota check. Per default only
user quota is checked. The user can configure if group quota should
be checked additionally.
Users and groups with no soft and hard limit are ignored for monitoring.
ID: 2310
Title: multisite view data export: fixed exception when using joined columns
Component: Multisite
Level: 1
Class: Bug Fix
Version: 1.2.7i2
The csv / json / python data export of a mulitsite view did not work correctly
when there were joined columns involved. An exception occured whenever an additional
column was set after the joined column.
Note: A single joined column at the end of a table row did work.
ID: 2354
Title: BI aggregations now also consider the service period
Component: BI
Level: 2
Class: New Feature
Version: 1.2.7i2
BI aggregations now also consider the service period of their contained
services and hosts - just like for downtimes and acknowledgements. A BI
aggregate is thus considered to be within its service period if its state
would be OK under the assumption that all objects that are currently out
of their service period are CRIT and the rest is OK. Or otherwise stated:
If all things that are not in their service period are switched off: if the
BI aggregate would get CRIT - well then it is not in its service period.
Yet in other words that means that the service period of something can only
cover times where all of its vital parts also are in service period.
The information "within/out of service period" is now also available for
the availability computations. That allows you now to base availability
reporting for BI aggregates to be based on certain time periods.
ID: 2332
Title: New icon for hosts/services that are out of their service period
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.7i2
The service period defines the times of the day that a service is expected
to by up. This is mainly being used for availability computations but can
also be used for filtering out unimportant things during non-work-hours.
ID: 2126
Title: cisco_ace_rserver: new check to monitor real servers of Cisco ACE servers
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i2