ID: 11137
Title: Monitor HP StoreOnce via new REST API 4.x
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
This werk enables the monitoring of a HP StoreOnce storage system via the REST API version 4.x and upwards. It is incompatible to the previously used API 3.x.
Use the software version of your HP StoreOnce appliance to choose the correct WATO rule:
<li> version > 4.x: Use WATO Rule "Check HPE StoreOnce via REST API 4.x"
<li> version < 4.x: Use WATO Rule "Check HPE StoreOnce"
ID: 11209
Title: aws_ec2_limits crashes on unhandled KeyError
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
aws_ec2_limits would crash on unknown resource keys which occur when the agent
returns with recource identifiers which are still unknown to Checkmk.
This fix makes the check return WARN together with a string containing the
unknown resource key instead.
ID: 11188
Title: Fixed non functional "discovery state" filter
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
The filter "discovery state", used in views like "Unmonitored services", had no
effect. From now on, the selected values are filtered correctly.
ID: 11191
Title: Fixed misleading snmp error message
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
In most cases, the reason for errors is not a missing system description OID
but missing firewall policies, misconfigured SNMP, wrong community, etc.
ID: 11082
Title: jobs: Exit codes of jobs can now be mapped to states
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
In previous versions, all exit codes except 0 were evaluated as CRITICAL. Now
it is possible to determine the evaluation of the exit codes in the check
parameters.
ID: 11189
Title: if.include: Better visualization of unicast and non-unicast packets
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
The graph "Packets" was showing unicast/non_unicast packets as area and
stacked. This way the non-unicast traffic was difficult to identify. From now
on unicast and non-unicast packets are shown as line.
ID: 11190
Title: if.include: Fixed description and help text for average option for used bandwidth
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
The option "Average values" in ruleset "Network interfaces and switch ports"
was renamed to "Average values for used bandwidth" and moved under the related
option. Also the help text was adjusted.
ID: 11187
Title: if.include: Added broad- and multicast packet rate monitoring
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
Broadcast and multicast packet rates can now be monitored.
You can define levels within the WATO rule "Network interfaces and switch
ports". To react only on long-time changes also averaging can be set.
ID: 11215
Title: Extension of the monitoring of UCS C-Series Rack Servers
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
This werk extends the special agent for monitoring UCS C-Series Rack Servers
to output information about LEDs and fault objects. It also adds two new checks
which monitor this data. The check ucs_c_rack_server_led monitors the colors of
all found LEDs and also provides their names and operational states. The check
ucs_c_rack_server_faultinst monitors fault objects such as degraded batteries.
It provides both a summary of all faults as well as detailed information about
each fault.
ID: 11153
Title: Averaging of single-core CPU utilization
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
This werk extends the following checks by an option to compute averaged
single-core CPU utilizations (previously, this was only possible for the total
CPU utilization): hr_cpu, huawei_switch_cpu, kernel.util, tplink_cpu,
winperf_processor.util. In particular, this option is now available for Linux/UNIX
(kernel.util) and Windows systems (winperf_processor.util).
To activate the averaging, use the option "Averaging for single cores" of the rules
"CPU utilization on Linux/UNIX" or "CPU utilization for simple devices" (depending on
the check). Note that, as described in the documentations of these rules, this option
only has an effect when used together with the sub-options "Apply single-core levels"
or "Graphs for averaged single-core utilizations".