ID: 13745
Title: Main folder not selectable when bulk moving hosts
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
When using bulk move to move hosts to another folder the Main folder
was not selectable in the dropdown menu.
ID: 14153
Title: dcd: resolving wrong format for phase_1 result
Component: Dynamic host configuration
Level: 1
Class: Bug fix
Version: 2.2.0i1
The dcd execute_phase1_result using the REST-API returned
the wrong data type compared to the Web-API. This resulted in
an internal server error on the dcd side. This werk fixes
this issue.
ID: 14088
Title: storcli_cache_vault: new plugin
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
This check monitors the status of cache vault units on controllers that are based on LSI Megaraid chipsets, if they support cache vautls.
The Linux agent will try find any existing controllers - if <tt>storcli</tt> or <tt>storcli64</tt> is in your PATH.
<tt>storcli</tt> can be downloaded <a href="https://docs.broadcom.com/docs/007.2007.0000.0000_Unified_StorCLI.zip">from LSI</a>
ID: 13650
Title: Updated rule export page for REST API
Component: REST API
Level: 1
Class: Bug fix
Version: 2.2.0i1
The rule export page of the Setup is needed to help users working with the new
rule related REST API endpoints.
To set the value of a rule using the REST API, you need to set the value_raw
field. The value of that field is individual for each rule set. To help you
understand what kind of data structure you need to provide, this rule export
mechanism is showing you the value you need to set for a given rule. The value
needs to be a string representation of a compatible Python data structure.
You can copy and use the data structure below in your REST API requests.
The previous export of the whole internal rule data structure was only relevant
for use with the now deprecated Web API and misleading when using the REST API.
For example the conditions field is represented differently for the REST API.
To get an idea of this data structure looks like, have a look at the REST API
documentation of the relevant endpoints.
ID: 14152
Title: KUBE kube_cpu: changing check parameters back to cpu default values
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Previously, the kube_cpu check plugin used the Kubernetes
memory ruleset instead of the cpu ruleset. This caused
some options to display the wrong default values. This
werk fixes this issue.
ID: 14070
Title: KUBE kube_resource_quota_cpu: addition of plugin
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
This werk adds the check plugin for the Kubernetes
Resource Quota CPU resources.
ID: 14128
Title: KUBE agent_kube: Option Monitor namespaces matches inline help
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Previously, if the option 'Monitor namespace' was used to filter namespaces, the performed search
would be a prefix search. This was inconsistent with the inline help, which promises a complete
search. With this werk, an infix search is now performed by the agent, which is the default in
Checkmk. Those users who have configured the option 'Monitor namespaces' to be sensitive to the
type of regex matching performed need to verify that the agent is still performing as expected.
ID: 14127
Title: KUBE agent_kube: Option Cluster resource aggregation matches inline help
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Previously, if the option 'Cluster resource aggregation' was used to exclude
Nodes based on their roles, the performed search would be a prefix search. This
was inconsistent with the inline help, which promises an infix search. With
this werk, an infix search is now performed by the agent. Those users who have
configured the option 'Cluster resource aggregation' to be sensitive to the
type of regex matching performed need to verify that the agent is still
performing as expected.
ID: 14129
Title: KUBE kube_pod_status: Option Interpretation of pod status matches inline help
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Previously, if the option 'Interpretation of pod status' was used to assign a
Pod to a group, the performed search would be a prefix search. This was
inconsistent with the inline help, which promises an infix search. With this
werk, an infix search is now performed by the agent. Those users who have
configured the option 'Interpretation of pod status' to be sensitive to the
type of regex matching performed need to verify that the agent is still
performing as expected.
ID: 14126
Title: KUBE agent_kube: clarify error messages caused by unsupported Kubernetes version
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
With this werk, the agent verifies whether the Kubernetes version is supported by Checkmk. If it is
known that an API server with a certain version is incompatible, the agent will now provide a
helpful error message. Different flavors of Kubernetes are not verified. In the event, that the
version of the API server deviates from the versioning scheme used by Kubernetes, processing the API
data is still attempted on a best effort basis. Errors related to unknown versioning schemes can be
inspected by increasing the verbosity of the agent via the command line (you can find the command
line tool by using cmk -D).