ID: 6708
Title: WATO service discovery: Fixed incorrect creation of disable rule for duplicate service description
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
Different check_types may have the same service description, for example <tt>CPU utilization</tt>.
If you created a <tt>Disabled check</tt> rule for some SNMP based CPU utilization check and
used the service discovery page, a <tt>Disabled service</tt> rule was automatically created for this SNMP
based check. As a side effect, the TCP based CPU utilization check was disabled as well..
ID: 7049
Title: oracle_logswitches: Fix interchanged lower levels
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Previously the warn and crit levels have been interchanged.
This werk fixes this issue.
CMK-1784
ID: 7244
Title: Restricted WATO sidebar snapin only show up to 10+ changes
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
The sidebar snapin and the WATO main page now use the same infotext to display the number of pending changes.
This infotext currently displays only up to 10 changes in detail. Any number above 10 is abstracted with the text <tt>10+ changes</tt>.
The reasoning behind this is, that there may be some sites with thousands of pending changes.
Determining the exact number generally takes some time, hereby slowing down the rending of any page showing this infotext.
The <tt>10+ changes</tt> limit may be lifted in the future, once a more performant changes measurement functionality has been introduced.
ID: 6763
Title: if_brocade: Fixed missing graph templates and units for metrics
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
The graph definitions and units for metrics have been missing for interface
services of several brocade devices, if they use if_brocade instead of the
regular if64 check plugin. This is now fixed.
ID: 7216
Title: Azure: Select resources by tags
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1
You can now use Azure resource tags to decide which azure resources should
be included in your monitoring using the datasource programs rule "Microsoft Azure".
ID: 7200
Title: check_mail_loop: Fixed 'option --subject not recognized'
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
When used in WATO, the 'subject' parameter was not called correctly in the check command.
This has been fixed.
ID: 7199
Title: heartbeat_crm: Fixed discovery of services in case of failed actions
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Because of changes in pacemaker in some cases wrong services named "Heartbeat CRM Failed"
where discovered if there are open failed actions.
This has been fixed.
If you already have discovered such services, you need to re-discover the services of the
affected hosts.
ID: 7238
Title: check_smtp: Float warning / critical thresholds can now be configured using the GUI
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
The active check check_smtp already supported floating point warning and critical
thresholds, but the GUI only accepted integral numbers.
ID: 6967
Title: Initialize step value for unknown metrics in rrddata columns
Component: Livestatus
Level: 1
Class: Bug fix
Version: 1.6.0i1
When unknown metrics were queried via rrddata Livestatus columns, the step
value was not initialized, so a more or less random value was returned.
Valgrind was of course unhappy about this, too. This has been fixed, and
the step value is now zero under such circumstances.
ID: 7196
Title: agent_prism: Fixed wrong usage and capacity detection
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
The special agent used the API endpoint "storage.usage_bytes" and "storage.capacity_bytes"
what leaded to wrong values. New used API endpoints are "storage.user_usage_bytes" and
"storage.user_capacity_bytes".