ID: 13980
Title: Validation for 'move rule' endpoint has been tightened
Component: REST API
Level: 1
Class: Bug fix
Version: 2.3.0b1
Before moving a rule before or after another rule, the REST API will now check if both rules belong to the same ruleset and are distinct rules.
ID: 15686
Title: Allow Links in HTML Emails
Component: Notifications
Level: 1
Class: Bug fix
Version: 2.3.0b1
With Werk #15069 escaping for the <tt>Insert HTML section between body and table</tt> section was introduced.
Unfortunately links were not allowed anymore.
This Werk removes the escaping for links.
Links (<tt>a</tt>) are now allowed with the attributes <tt>href</tt> and <tt>target</tt>.
The <tt>href</tt> needs to be either relative or when absolute must use one of the following URL schemas: <tt>http</tt>, <tt>https</tt>, <tt>mailto</tt>.
ID: 15667
Title: mk-job.{aix,solaris}: silently handle missing write permissions to $MK_VARDIR/job errors
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.3.0b1
The Linux variant mk-job does not report any errors in the event the user
running the jobs does not have write permissions to the $MK_VARDIR/job
directory (i.e. errors of this kind are not written to stderr). This feature is
now also available for mk-job under Solaris and AIX.
ID: 15676
Title: group_config: delete endpoints now return a 409 when is use.
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.3.0b1
This werk introduces a fix to the contact_group_config,
host_group_config and service_group_config delete endpoints.
When the groups were in use, they were incorrectly returning
a 400 response. We now return a 409 Conflict response.
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: 15531
Title: fortigate_sensors: Discover additional devices
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
The SNMP detection of the plugin <i>"FortiGate Firewalls: Sensor Summary"</i> has been needlessly restrictive.
The plugin will now be triggered for additional devices.
ID: 15464
Title: agent_azure: azure_agent_info is no longer CRIT if there are no usage details
Component: agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
Azure Agent Info service is no longer CRIT if cost details are missing.
If there are no running Azure services that create costs, there
will be no usage details. Since that is a valid use case, we now show
a 'Usage client: Azure API did not return any usage details' message,
but the status of the service remains OK.
ID: 15553
Title: time_period: making time-related validation more strict
Component: REST API
Level: 1
Class: Bug fix
Version: 2.3.0b1
Prior to this werk, the REST API was quite lenient when it came
to specifying a time allowing the format hh:mm for some while asking
the hh:mm:ss format for others. This werk targets the active_time_ranges
field where now a hh:mm:ss format is enforced.
Due to the introduction of the more strict pattern, user scripts must be
adjusted accordingly to respect the new format.
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: 15450
Title: mk-job: improvements to state file persistence
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
The mk-job agent plugin saves information about a job's running and completed
states in files under $MK_VARDIR/job. These files were written dynamically and
this could give rise to situations in which the state file was read while
information was being written to it. The information within the <<<job>>>
section could therefore be confusing and incomplete. This has been improved by
introducing atomic operations: files are now either present and complete, or
absent altogether.