ID: 10460
Title: Show an error in the tactical overview if sites are not connected
Component: Multisite
Level: 1
Class: New feature
Version: 1.7.0i1
If a remote site is not connected in a distributed setup the hosts,
services and events of that site are not taken into account in the
tactical overview of the master site. To indicate that information
is missing the tactical overview now displays an error if sites are
not connected. The error is displayed below the rows of the tactical
overview similar to failed notifiactions.
ID: 10461
Title: Duplicate entries in BI Aggregation Groups snapin
Component: BI
Level: 1
Class: Bug fix
Version: 1.7.0i1
Aggregation groups with the same name appeared multiple
times in the BI Aggregation Groups snapin. Furthermore the
aggregation groups in filters and the BI Aggregation Groups
Tree snapin were not sorted alphabetically. This is fixed.
ID: 10410
Title: brocade_fcport: use 64bit counters for tx/rx frames
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
On high-speed interfaces, the 32bit counters may wrap very often and make
the counters unusable. 64bit counters track traffic appropriately, thus
they are preferred when available.
The 64bit counters are already used for tx/rx words and bbcredits
ID: 10606
Title: Several minor GUI fixes
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
Fixed the theme specific coloring of list collapsing icons.
Adjusted the padding for search bars in long WATO lists.
Fixed the OK state font color in the "Analyze configuration" view for the dark theme.
ID: 10473
Title: aix_diskoid,hpux_lunstats: Allow Disk IO SUMMARY for indiviual nodes of a cluster
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Previously the SUMMARY service of theses Disk IO Checkplugins reported UNKNOWN for every
individual node as soon as the node was part of a cluster. This has been fixed.
ID: 10424
Title: informix_tabextents: Addition of WATO rule configuration
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
The manpage for the informix_tabextents details that a WATO rule can be configured
to set the levels for the number of table extents. This WATO rule has now been
added in this werk.
ID: 10290
Title: Temperature check GUI: fix rendering crash when rules are set
Component: WATO
Level: 2
Class: Bug fix
Version: 1.7.0i1
10290 FIX Temperature check: fix rendering crash and reporting mismatch
When a check sends a device-specific levels in a specific format
the temperature rendering function of the service display
could crash due to a type mismatch. This werk fixes this crash.
Upon fixing this crash another bug was discovered and fixed. In the case
of user specified levels being set and the service being in mode
"Use your own levels if present, otherwise the device's", the device
levels were not ignored and thus the wrong levels were checked. This
is now fixed as well.
No additional action is needed.
ID: 10442
Title: selection of host dropdowns now possible with arrow keys
Component: Multisite
Level: 1
Class: New feature
Version: 1.7.0i1
The selection of autocomplete host dropdown fields is now possible by using the up and down arrow keys.
These dropdown field can for example be found in every rule in the 'Explicit hosts' section.
ID: 10500
Title: postfix_mailq: Also discover the default queue which can exist even if multiple instances are configured
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
If multiple instances are configured the postfix mail queue check also
discovers the default queue which was missing before. The default queue name is
{{}} (empty) for non-multi and multi Postfix environments.
ID: 10451
Title: check_http: don't set virtual host if not necessary
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Since version 1.6 the active check check_http automatically
set the HTTP Host header and used HTTP/1.1 instead of HTTP/1.0
even if no virtual host was supplied. This may lead to
timeouts of the check_http plugin on servers which are not
fully compliant with HTTP/1.1.
This werk changes this behaviour so that the Host header is
only set if a virtual host is given.
Please note that if you rely on HTTP/1.1 or want to use it you
have to supply a virtual host.
Please also note that the virtual host will not be set
automatically to the host name anymore. If you relied on this
behaviour you now have to provide the virtual host in the
affected rules.