ID: 15445
Title: SAML metadata endpoint: support HEAD requests
Component: setup
Level: 1
Class: New feature
Version: 2.3.0b1
Some identity providers (e.g. Net IQ) require the HTTP headers first in order
to import the XML metadata. The Checkmk metadata endpoint for SAML now supports
this request method.
ID: 15135
Title: New option to share views, dashboards and report definitions
Component: Multisite
Level: 2
Class: New feature
Version: 2.3.0b1
This feature was requested via the feature portal:
https://features.checkmk.com/suggestions/297892/make-dashboards-also-mkpable
You now have the option to export views, dashboards and reports (so called
visuals). They can be downloaded, versioned, and shared with other Checkmk
installations.
The following example describes the new feature for views (it works the same
way for all types):
Users with permission "Manage Extension Packages (MKPs)" will see a new icon
for exporting the related view within "Customize" - "Views" for any none builtin
view.
If you use this icon, a new view will appear within the new section
"Extensions" and a file will be created within
'~/local/lib/check_mk/gui/plugins/views'.
Local files for dashboards will be stored in
'~/local/lib/check_mk/gui/plugins/view/dashboard', for reports they will be
stored in '~/local/lib/check_mk/gui/plugins/view/reports'.
With the 2 icons in the section "Extensions" you can go to the extension
package module and create an extension package or remove the related view from
the extension package page. The later will remove the file in the mentioned
local directory and the view from the "Extensions" section.
The "Extension" section also shows the state for each exported view, like "This
view can be packaged with the extension packages module." if the view was
exported and "This view is provided via the MKP 'MY_MKP'." if the view is part
of an installed extension package.
If the view is part of an extension package, you have the option to clone and
customize it.
ID: 14591
Title: Electrical Power for Devices with only one phase: Remove error message during discovery
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
During discovery the following error could occur
C+:
Invalid check parameter: The datatype must be a tuple, but is dict
Variable: checkgroup_parameters:epower_single
Parameters:
{}
C-:
This error is cosmetic in nature and does not affect the behaviour of the check.
This werk fixes the issue.
ID: 14592
Title: PSU Capacity Levels: Remove error message during discovery
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
During discovery the following error could occur
C+:
Invalid check parameter: PSU Capacity Levels: The value 80 has type int, but must be of type float
Variable: checkgroup_parameters:hw_psu
Parameters:
{'levels': (80, 90)}
C-:
This error is cosmetic in nature and does not affect the behaviour of the check.
This werk fixes the issue.
ID: 15254
Title: Fixed incorrect availability calculation when a host was removed and added again
Component: cmc
Level: 1
Class: Bug fix
Version: 2.3.0b1
The availability information was not updated when a new host got
re-introduced and the CMC was only reloaded, which resulted in "No
information about that period of time available" for such a host. Only a
CMC restart fixed the calculation, but with this fix a reload is enough.
ID: 15456
Title: mailbox: Fix exchangelib warning in the service summary
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
Previously, a warning "WARNING:exchangelib.account:Failed to guess local timezone. Fallback to UTC"
was shown in the mailbox service summary on some of the Checkmk servers.
ID: 14306
Title: DCD and InfluxDB configuration now respect "pretty print configuration files" option
Component: Setup
Level: 1
Class: Bug fix
Version: 2.3.0b1
The configuration files for DCD and InfluxDB are now saved in pretty printed format in
case the global setting "Pretty-Print configuration files" is enabled.
ID: 14590
Title: Agents identify themselves via User-Agent string
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.3.0b1
With this werk the HTTP(s) requests sent by agents have been updated to have a more consistent User-Agent string.
The following agents are affected.
LI: <tt>apache_status</tt> uses <tt>checkmk-agent-apache_status-2.3.0p1</tt>
LI: <tt>nginx_status</tt> uses <tt>checkmk-agent-nginx_status-2.3.0p1</tt>
LI: <tt>mk_jolokia</tt> uses <tt>checkmk-agent-mk_jolokia-2.3.0p1</tt>
LI: <tt>agent_jolokia</tt> uses <tt>checkmk-special-jolokia-2.3.0p1</tt>
LI: <tt>agent_vsphere</tt> uses <tt>checkmk-special-vsphere-2.3.0p1</tt>
LI: <tt>agent_netapp</tt> uses <tt>checkmk-special-netapp-2.3.0p1</tt>
LI: <tt>agent_splunk</tt> uses <tt>checkmk-special-splunk-2.3.0p1</tt>
The version at the end depends on the <tt>__version__</tt> of the agent.
If the shipped (unmodified) agent is used it will match the Checkmk version of the site.
ID: 15434
Title: agent: return better respones for GET collection
Component: REST API
Level: 1
Class: Bug fix
Version: 2.3.0b1
Previously when calling the agent GET collection endpoint, the
value attribute would only contain the following information for
each agent
C+:
{
"domainType": "dict",
"title": "e660531752c87c6c"
}
C-:
It now contains the following
C+:
{
'domainType': 'agent',
'extensions': {},
'id': 'a3e050556d2455c2',
'links': [
{
'domainType': 'link',
'href': 'http://localhost/heute/check_mk/api/1.0/objects/agent/a3e050556d2455c2',
'method': 'GET',
'rel': 'self',
'type': 'application/json'
}
],
'members': {},
'title': 'Agent a3e050556d2455c2'
}
C-: