ID: 10782
Title: Agent bakery generator for sap.cfg
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
The Agent bakery now correctly joins CCMS paths to be monitored when
generating the sap.cfg file for the SAP R/3 Monitoring pluging.
ID: 11124
Title: Arista BGP check plugin
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
Generates service info from basic BGP information provided via SNMP (LocalAddr, LocalIdentifier,
RemoteAs, RemoteIdentifier, AdminStatus, (Peer)State, LastErrorReceivedText). Check is always OK
and has no parameters.
ID: 11029
Title: Prevent duplicated rule packs when updating mkp
Component: Event Console
Level: 1
Class: Bug fix
Version: 1.7.0i1
If a mkp contains event console rule packs and is updated with a new version,
the rules are added to the existing rule pack configuration. This leads to duplicated entries.
>From now on, the related entry is updated in the rule configuration.
ID: 11079
Title: Grafana: Annotation queries were not applying host filter
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
When using the annotations feature of our Grafana connector, the
explicit host filter provided by Grafana was not used correctly.
This made Checkmk respond with annotations to unrelated hosts.
The host regex filter was applied correctly
ID: 11044
Title: dell_idrac_fans: don't crash on unknown device states
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
The check plugin crashed when fans of a device were in
states that did not return a device reading. The plugin
now returns only the status and the name for the states
"other", "unknown", and "failed".
Fans that are in the states "unknown" or "other" will
now no longer be discovered. Fans that are in the state
"failed" will still be discovered.
ID: 11145
Title: check_mk_agent.linux: exclusion of autofs in df section
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
This change introduces a new exclusion entry (autofs) for the df section. This can
potentially resolve problems if separate autofs information are provided.
ID: 11026
Title: Consider timespecific parameters for manual checks
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
If set, timespecific parameters of manual checks had no impact. From now on
such parameters are taken into account.
ID: 11078
Title: Dynamic configuration: Add connector plugin API
Component: DCD
Level: 2
Class: New feature
Version: 1.7.0i1
The Dynamic configuration is now loading plugins that are located below
the path <tt>local/lib/check_mk/cee/dcd/plugins/connectors/</tt>.
You can find a minimal example connector implementation it in your site at
<tt>lib/check_mk/cee/dcd/plugins/connectors/example_connector.py</tt>. You may
use this as base for your own connectors. To enable this connector, you need to
copy it to the plugin directory mentioned above and uncomment the registry
registration lines in the plugin (See TODO).
To be able to configure connections based on this connector in the GUI, you
also need to deploy a GUI plugin. An example can be found in your site at
<tt>lib/check_mk/gui/cee/plugins/wato/example_dcd_connector.py</tt>. This
needs to be placed in the WATO plugin directory of your site. You also need to
uncomment the registry registration line in the plugin (See TODO).
ID: 11096
Title: hyperv_vms: use default levels instead of discovered state
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
The check hyperv_vms now uses a set of default levels to map the
state of VMs to monitoring states. Before, by default, the check
compared the current VM state against the state at the point when
the service was discovered and went CRIT if the two states did not
match. This behavior is still available, but the check now has to
be specifically configured to do this, see the rule "State of
Microsoft Hyper-V Server VMs".
Furthermore, the check now always works when executed as a manual
check. Before, it might have crashed in this case, depending on
the used configuration.
This change is incompatible in the sense that users have to adjust
the rules for this check to make it behave the way it did before.