ID: 15477
Title: New option to migrate users to another user connector
Component: Setup
Level: 2
Class: New feature
Version: 2.3.0b1
You can now migrate existing users to another user connector, e.g. users with
connector "htpasswd" to a SAML or LDAP connector.
The option "Migrate users" is available within "Setup" - "Users" in the page
menu "Users" for users with permission "Migrate users to another connection".
Please note: The option is disabled if there is only one active user connector
configured.
To migrate users, please select the desired users on the "Users" page and use
the page menu entry "Migrate users". On the next page you have to choose the
target user connector and optionally, user attributes to unset on migration.
With "Migrate selected users" you will be aksed if you want to start the
migration. If you choose "Migrate" you will see a summary of migrated users and
possible problems that occurred during the migration.
ID: 15660
Title: Temperature unit in graphs and perfometers is now user-configurable
Component: metrics
Level: 2
Class: New feature
Version: 2.3.0b1
The temperature unit used to render graphs and perfometers is now configurable on a per-user basis
via the user profile. Users can either explicitly choose between degree Celsius and degree
Fahrenheit or they can use the default temperature unit, which in turn is configurable via a global
setting (linked in the user profile).
Note that this new setting does not affect the temperature unit used in service outputs (summary and
details). Use the ruleset <i>Temperature</i> to configure this.
Finally, with this new feature, the option to configure
<a href="https://checkmk.com/werk/14534">unit conversions in graphs tunings</a> is deprecated. This
option was specifically introduced to make the temperature unit in graphs user-configurable, which
is now possible via the setting introduced in this werk. Hence, unit conversions are no
longer configurable via graph tunings and any already exisiting settings will be ignored.
ID: 14953
Title: Fix broken "Agent controller auto-registration" rule after site rename or copy
Component: Setup
Level: 2
Class: Bug fix
Version: 2.3.0b1
Previously, after site rename or copy, the name of the site in the rule
"Agent controller auto-registration (Cloud Edition)" has not been changed
for the target site. This made baking the agent without fixing the rule
impossible.
With this release the problem has been eliminated.
ID: 15255
Title: Fixed removal of persistent acknowledgements
Component: Multisite
Level: 2
Class: Bug fix
Version: 2.3.0b1
Due to a regression introduced in 2.1.0, it was not possible anymore to
remove the comment part of persistent acknowledgements via the GUI. This
has been fixed.
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: 15243
Title: Automatic creation and registration of hosts
Component: Setup
Level: 2
Class: New feature
Version: 2.3.0b1
Users of the Checkmk Cloud Edition can now create an agent package that will automatically add the host to the monitoring upon installation.
If monitoring site and agent package are configured accordingly, the agent controller will contact the (remote) monitoring site, and post a request for registration.
The (central) site will then process this request according to its configuration and potentially create a new host in the monitoring, discover the services and start monitoring it.
Details can be found in the <a href="https://docs.checkmk.com/2.2.0/en/hosts_autoregister.html">user manual</a>.
ID: 15244
Title: New agent configuration: Push mode
Component: agents
Level: 2
Class: New feature
Version: 2.3.0b1
Users of the Checkmk Cloud Edition now have a new mode of operation for the agent controller at their disposal:
The "<i>Push mode</i>".
In the push mode, the Checkmk agent sends the monitoring data to the Checkmk server once per minute.
The agent pushes the data transmission on its own and does not wait for a request from the server.
The push mode is always required if the Checkmk server cannot access the network in which the host to be monitored and its agent are located, for example, in a cloud-based configuration.
More on the setup can be found in our <a href="https://docs.checkmk.com/2.2.0/en/agent_linux.html">user manual</a>.
ID: 14948
Title: Inline SNMP Backend uses credentials correctly
Component: inline-snmp
Level: 2
Class: Bug fix
Version: 2.3.0b1
Previously, the microcore had to be restarted to apply the change of SNMPv3
credentials for inline SNMP backend made in the GUI.
This fix solves the problem.
ID: 14583
Title: Fix attribute update and deletion of existing hosts
Component: Dynamic host configuration
Level: 2
Class: Bug fix
Version: 2.3.0b1
Previously, the dcd would stop updating and deleting the host configurations, if they were in
an inconsistent state. The following error would be shown:
C+:
k: api_attributes[k] for k in future_attributes["locked_attributes"] + internal_keys
KeyError: 'site'
C-:
With this werk, the dcd will not crash. Instead it assigns the attributes, which are configured by
the connection.
ID: 14875
Title: shadow hosts custom attributes doesn't disappear anymore
Component: config
Level: 2
Class: Bug fix
Version: 2.1.0p15
Previously, shadow hosts custom attributes were ignored during
config generation.
With this release the problem has been eliminated.