[//]: # (werk v2)
# Reporting: Add time range options for first/last work day of this/last month
key | value
---------- | ---
date | 2024-04-15T09:44:50+00:00
version | 2.3.0b6
class | feature
edition | cee
component | reporting
level | 1
compatible | yes
When creating/editing a report users can now select the following additional options within the report property "Default time range":
* "First work day of this month"
* "Last work day of this month"
* "First work day of last month"
* "Last work day of last month"
Note that these time ranges do not consider holidays.
[//]: # (werk v2)
# Licensing: Reset license state when updating from Enterprise to non-Enterprise
key | value
---------- | ---
date | 2024-04-17T16:10:14+00:00
version | 2.3.0b6
class | fix
edition | cee
component | setup
level | 1
compatible | no
When upgrading from an Enterprise to another edition is performed, the site will start a new trial period, even if licensing credentials had already been configured.
To license the product, a license verification needs to be performed (on the licensing page: Setup > Maintenance > Licensing > Online/Offline verification).
[//]: # (werk v2)
# ldap: show the correct customer for ldap users
key | value
---------- | ---
date | 2024-04-18T14:03:11+00:00
version | 2.3.0b6
class | fix
edition | cme
component | wato
level | 1
compatible | yes
When an ldap connection is configured for a specific customer, this
wasn't reflected in the users for that ldap connection. This werk
addresses this issue by now showing the correct customer.
[//]: # (werk v2)
# Support Diagnostics: The timeout for creating a dump is now configurable
key | value
---------- | ---
compatible | yes
version | 2.3.0b6
date | 2024-04-12T11:07:00+00:00
level | 1
class | feature
component | wato
edition | cre
Before this werk, the process of creating a Support Diagnostics Dump sometimes lead to a timeout exception. The hard-coded timeout was 110s.
Now, it's possible to configure the timeout in the user interface.
[//]: # (werk v2)
# Synthetic Monitoring: Incompatible overhauls
key | value
---------- | ---
date | 2024-04-17T11:05:50+00:00
version | 2.3.0b6
class | feature
edition | cee
component | checks
level | 1
compatible | no
This werk only affects users who have configured the rule *Robotmk scheduler (Windows)* during the
2.3.0 beta phase. The following incompatible changes have been made:
* The plan naming convention introduced in [werk 16421](https://checkmk.com/werk/16421) has been adopted in more places, both internally and user-facing.
* The service items of the *RMK Plan* and *RMK Test* services have been reworked to include the name of the corresponding top-level Robot Framework suite.
* Previously, the scheduler terminated in case of permission issues for example with its working directory. As of this werk, the scheduler instead skips affected plans and forwards these issues to the Checkmk server, where they are reported to the user.
After updating, the *RMK scheduler status* service will report UNKNOWN. The plan and test services
will go stale. Furthermore, the *Check_MK* service will report that there is monitoring data missing
for the plugins `robotmk_plan` and `robotmk_test`. To remedy these issues, users first have to re-
bake and then update the Checkmk agent on affected systems. After updating the agent, users have to
re-discover the services of affected Checkmk hosts.
Werk 16606 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# agent_netapp_ontap: handle shelves without elements
key | value
---------- | ---
date | 2024-04-10T12:26:35+00:00
version | 2.3.0b6
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The agent did not handle the cases where shelves had no fans, temperature sensors or PSUs.
This led to crashes during the agent execution.
With this werk we now correctly handle these scenarios and the corresponding services are not discovered if no items are found.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# agent_netapp_ontap: handle shelves without elements
key | value
---------- | ---
date | 2024-04-10T12:26:35+00:00
- version | 2.3.0b5
? ^
+ version | 2.3.0b6
? ^
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The agent did not handle the cases where shelves had no fans, temperature sensors or PSUs.
This led to crashes during the agent execution.
With this werk we now correctly handle these scenarios and the corresponding services are not discovered if no items are found.
Werk 16690 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# pfsense_if: stale services in 2.3 beta
key | value
---------- | ---
date | 2024-04-17T11:38:38+00:00
version | 2.3.0b6
class | fix
edition | cre
component | checks
level | 1
compatible | yes
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# pfsense_if: stale services in 2.3 beta
key | value
---------- | ---
date | 2024-04-17T11:38:38+00:00
- version | 2.3.0b5
? ^
+ version | 2.3.0b6
? ^
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Werk 16423 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# mk_postgres.py: Add 'PG_BINARY_PATH' to Bakery Rule
key | value
---------- | ---
date | 2024-04-16T15:15:06+00:00
version | 2.3.0b6
class | feature
edition | cee
component | agents
level | 1
compatible | yes
[Werk #15619](https://checkmk.com/werk/15619) added support for reading `PG_BINARY_PATH` from
`postgres.cfg`. This Werk allows setting this value with the agent bakery.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# mk_postgres.py: Add 'PG_BINARY_PATH' to Bakery Rule
key | value
---------- | ---
date | 2024-04-16T15:15:06+00:00
- version | 2.3.0b5
? ^
+ version | 2.3.0b6
? ^
class | feature
edition | cee
component | agents
level | 1
compatible | yes
[Werk #15619](https://checkmk.com/werk/15619) added support for reading `PG_BINARY_PATH` from
`postgres.cfg`. This Werk allows setting this value with the agent bakery.
[//]: # (werk v2)
# postgres_stat_database_size: Don't discover 'access_to_shared_objects'
key | value
---------- | ---
date | 2024-04-16T07:10:21+00:00
version | 2.3.0b6
class | fix
edition | cre
component | checks
level | 1
compatible | no
Checkmk discovered Services like "PostgreSQL DB MAIN/access_to_shared_objects
Size" but the Services only showed "Database size not available" and a WARN
status.
Those Services are no longer discovered.
[//]: # (werk v2)
# Inventory: Add Windows support for Hardware > System > Uuid
key | value
---------- | ---
date | 2024-04-16T13:09:47+00:00
version | 2.3.0b6
class | feature
edition | cre
component | inv
level | 1
compatible | yes
This element is already available for Linux, now the windows agent also supports
reading this value.
You have to update `mk_inventory.vbs` on the monitored host, to provide the
necessary data.