ID: 14940
Title: Fix hex to rgb color conversion
Component: metrics
Level: 1
Class: Bug fix
Version: 2.2.0i1
Hex to RGB conversion has now been fixed to work for 3-digits HEX
If you had an error showing "Invalid color specification: #100" in the
graph, this will be fixed by this werk.
ID: 15233
Title: Discovery: Improve performance and prevent apache timeout
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0p21
This Werk prevents an undesired SNMP scanning process during service discovery.
This additional scan increased the time the discovery took by a factor of two.
In addition, no progress was reported for the first of the scans, which could result in an apache timeout after 110 seconds.
In that case the message shown was
<i>
Your request timed out after 110 seconds.
This issue may be related to a local configuration problem or a request which works with a too large number of objects.
But if you think this issue is a bug, please send a crash report
<i>.
ID: 15209
Title: host_config: fix host attribute IPv6 address validation
Component: REST API
Level: 1
Class: Bug fix
Version: 2.2.0i1
Prior to this werk, the REST API failed with a 500 error if the
user tried to query or create a host with a valid Host- or DNS
name as Ipv6 address.
This restriction also caused an error in the DCD as it is reliant
on the the list all hosts endpoint.
This werk resolves both issues.
ID: 15175
Title: Interface checks: re-work misleading bandwidth levels configuration
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
When configuring bandwidth levels, users previously configured
NL: Traffic direction: in / out / both
NL: Are the tresholds upper or lower thresholds?
NL: Threshold type: absolute / relative to interface speed / predictive
NL: Specific settings for selected threshold type
However, when selecting predictive levels, users had to again configure settings for upper and/or
lower thresholds. In this case, the outer setting (number 2 from the list above) had no effect.
Hence, the new configuration looks like this:
NL: Traffic direction: in / out / both
NL: Threshold type: absolute / relative to interface speed / predictive
NL: Specific settings for selected threshold type, including upper/lower setting
ID: 15208
Title: users: fix error when changing the password for an existing user
Component: Setup
Level: 1
Class: New feature
Version: 2.2.0i1
Prior to this werk, an error was raised when an user tried to change the
password for an existing user if the DCD global setting was not configured.
This werk resolves the issue.
ID: 15211
Title: ActivateChanges: Improvements to what data is returned to the API user
Component: REST API
Level: 1
Class: Bug fix
Version: 2.2.0i1
When activating changes or requesting running changes via the REST API,
the response would only contain activation ID. This werk adds more
information to the returned activation data, for example, the changes
made, the sites affected etc.
ID: 14577
Title: KUBE: Requests utilization now supports lower levels
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
The new option can be configured in the rules <tt>Kubernetes resource quota cpu
utilization</tt>, <tt>Kubernetes CPU resource utilization</tt>, <tt>Kubernetes
resource quota memory utilization</tt> and <tt>Kubernetes memory resource
utilization</tt>.
ID: 15122
Title: New option to make customizations available to users of selected sites
Component: Multisite
Level: 2
Class: New feature
Version: 2.2.0i1
You can now make customized views, dashboards, etc. available for users on
selected sites.
Therefore new permissions like "Publish views to users of allowed sites" are
introduced and assigned to the "admin" role.
With this permission you can use the option "Make this view available for other
users" - "Publish to users of sites" on the "Edit" page of the customization.
Please note that the customizations will be available on the selected sites
after the next activation of changes for these sites.
ID: 14579
Title: KUBE: Allow configuration of roles belonging to a control plane node
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
With this werk, you can specify roles of a control plane node via the rule <tt>Kubernetes node
count</tt>. If a node has any of these roles, then it is considered a control plane node by
Checkmk. Otherwise, it is considered a worker node.