ID: 3840
Title: cisco_qos: Fixed wrong units in graphs
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.4.0i1
The used units in graphs for QoS-Services changed from bytes/s to bits/s
and is now equivalent to other network service graphs.
ID: 3879
Title: ipmi, ipmi_sensors: unified ipmi checks which now work the same way
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.4.0i1
Default discovery rule of ipmi is "summary mode", the one of ipmi_sensors is "single mode".
ID: 3878
Title: apc_symmetra: divided into several checks
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.4.0i1
Now the check is more clearer and each check has its own, already
existing WATO group.
The separation of apc_symmetra is as follows:
- apc_symmetra monitors some states and battery aspects (as before)
- apc_symmetra.temp reports the battery temperature
- apc_symmetra.elphase reports the battery current
- apc_symmetra_input checks the electrical inphase
- apc_symmetra_output checks the electrical outphase
ID: 3812
Title: winperf_phydisk: reintroduced read and write queue length performance data
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.4.0i1
These values were lost due to a recent code refactoring.
ID: 3887
Title: Event contact groups are now handled in notifications (optionally)
Component: Event Console
Level: 2
Class: New Feature
Version: 1.4.0i1
Previously you could already configure contact groups in Event Console rules,
but those groups were only used to control the visibility of the events in
the GUI.
Now these groups can be used to control the visibility and also make them
relevant for the notifications created by the Event Console. Besides adding
the groups to the rule, you can configure whether or not to add the contact
groups to the notifications and also configure the precedence of the groups
in case there are host contact groups configured and event contact groups
in the rule.
Existing rules are treated as before. The contact groups of the rule will
not be added to the notifications until you open the rule, tick the checkbox
and save the rule again.
ID: 3811
Title: HW/SW Inventory: Fixed GUI display crash when querying data from older software versions
Component: HW/SW-Inventory
Level: 1
Class: Bug Fix
Version: 1.4.0i1
Older software (livestatus) versions did not provide sufficient inventory data.
The crash happened when a site with a newer software version tried to query
data from a site running an older version.
ID: 3877
Title: ibm_tl_changer_devices, ibm_tl_media_access_devices, ibm_tl_scsi_prot_ctrl: new checks for IBM tape library which support the SNIA-SML and SML MIB.
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.4.0i1
ID: 3886
Title: Notifications that do not match any rule are sent to fallback mail / contacts
Component: Notifications
Level: 1
Class: New Feature
Version: 1.4.0i1
When a notification is received and is not matched by any notification rule, it could
be sent to a globally configured and optional fallback email address.
So, if you did not configure this fallback email address, it was possible that generated
notifications, e.g. from the Event Console, were not sent to any user.
This has been extended so that you can either configure the global mail address or set
and attribute for your user accounts individually. For each of your users you can now
set the flag "Receive fallback notifications".
Another change: If you use the rule based notifications and have not configured any
fallback contact (either globally or user), there will be a warning message displayed
on the notification configuration page.
Another change: When having a notification rule that has a condition on contact groups,
or any user creates a custom notification rule, and a notification was generated which
had no contact group information at all, the notification was sent to ALL users, instead
of none.
That was implemented this way just to be sure that the notifications are not suppressed
by accident. This has been changed to be also processed like other notifications that
do not match any rule. Finally these notifications will be handled with the configured
fallback contacts.