Werk 16791 was deleted. The following Werk is no longer relevant.
[//]: # (werk v2)
# Fix categorization of some rule specs using new Ruleset API
key | value
---------- | ---
date | 2024-04-19T12:04:19+00:00
version | 2.3.0p1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The following rule specs/topic combinations from cmk.rulesets.v1 will now be shown in different categories in the UI
* SpecialAgent with Topic.CLOUD: under `Setup > Agents > VM, cloud, container`
* AgentConfig with TOPIC.LINUX: under `Setup > Agents > Windows, Linux, Solaris, AIX > Agent rules > Linux Agent` (not available in Raw)
* AgentConfig with TOPIC.WINDOWS: under `Setup > Agents > Windows, Linux, Solaris, AIX > Agent rules > Windows Agent` (not available in Raw)
* AgentConfig with TOPIC.GENERAL: under `Setup > Agents > Windows, Linux, Solaris, AIX > Agent rules > Generic Options`
* AgentConfig with another topic: under `Setup > Agents > Windows, Linux, Solaris, AIX > Agent rules > Agent plug-ins` (not available in Raw)
[//]: # (werk v2)
# Dashboard element "Site overview": enable larger hexagon rendering
key | value
---------- | ---
date | 2024-04-24T06:56:55+00:00
version | 2.3.0p1
class | feature
edition | cee
component | multisite
level | 1
compatible | yes
In the properties of the dashboard element "Site overview" users can now set the "Maximum hexagon size" to either "Default" or "Large". Rendering large hexagons can be useful when displaying the dashboard element on a large screen, as e.g. on a wall monitor.
[//]: # (werk v2)
# agent_gcp: reduced query rate
key | value
---------- | ---
date | 2024-03-25T12:43:27+00:00
version | 2.3.0p1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
An exception was sometimes raised for an excessive frequency of queries to the GCP API.
The agent now queries the GCP API once per metric.
[//]: # (werk v2)
# Fix categorization of some rule specs using new Ruleset API
key | value
---------- | ---
date | 2024-04-19T12:04:19+00:00
version | 2.3.0p1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The following rule specs/topic combinations from cmk.rulesets.v1 will now be shown in different categories in the UI
* SpecialAgent with Topic.CLOUD: under `Setup > Agents > VM, cloud, container`
* AgentConfig with TOPIC.LINUX: under `Setup > Agents > Windows, Linux, Solaris, AIX > Agent rules > Linux Agent` (not available in Raw)
* AgentConfig with TOPIC.WINDOWS: under `Setup > Agents > Windows, Linux, Solaris, AIX > Agent rules > Windows Agent` (not available in Raw)
* AgentConfig with TOPIC.GENERAL: under `Setup > Agents > Windows, Linux, Solaris, AIX > Agent rules > Generic Options`
* AgentConfig with another topic: under `Setup > Agents > Windows, Linux, Solaris, AIX > Agent rules > Agent plug-ins` (not available in Raw)
[//]: # (werk v2)
# Bi: service/host_label group operator now has a default operator key "and"
key | value
---------- | ---
date | 2024-04-29T11:10:04+00:00
version | 2.3.0p1
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
When creating Bi rules via the REST-API, the host_label_groups and
the service_label_groups fields both accepted a list of conditions.
These conditions previously required an operator field. However,
we realized that the operator field for the first item in these lists
really wasn't needed and had no affect. So that the user doesn't have
to provide this value, we have now added a default value for all
conditions in this list of "and".
[//]: # (werk v2)
# Pure Storage FlashArray: Devices with status 'not_installed' will now have an OK state
key | value
---------- | ---
date | 2024-04-28T17:04:15+00:00
version | 2.3.0p1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Devices with a reported status of 'not_installed' previously caused the check state to be CRIT.
This behaviour has now been changed. These devices will now have an OK state.
[//]: # (werk v2)
# infoblox_temp: Add support for Nios version > 8.6
key | value
---------- | ---
date | 2024-04-26T06:56:26+00:00
version | 2.3.0p1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The relevant OIDs have changed for newer Nios versions. The check now differentiates between the different version, meaning the check does not crash anymore when parsing newer sections.
[//]: # (werk v2)
# Fix crash on user page with SAML connector
key | value
---------- | ---
date | 2024-04-29T12:01:22+00:00
version | 2.3.0p1
class | feature
edition | cee
component | wato
level | 1
compatible | yes
When viewing the users page with a user using a SAML connector a crash report
with "Internal error: locked" was shown. This is fixed now.
Werk 16528 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# reports: remove site_id of other customers when rendering reports
key | value
---------- | ---
date | 2024-04-18T07:21:06+00:00
version | 2.3.0p1
class | fix
edition | cme
component | reporting
level | 1
compatible | yes
When you try to create a report and a remote site is not reachable, the
report will include the site_id of said site. This werk addresses this
issue by only showing errors that belong to that customer.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# reports: remove site_id of other customers when rendering reports
key | value
---------- | ---
date | 2024-04-18T07:21:06+00:00
- version | 2.3.0b7
? ^^
+ version | 2.3.0p1
? ^^
class | fix
edition | cme
component | reporting
level | 1
compatible | yes
When you try to create a report and a remote site is not reachable, the
report will include the site_id of said site. This werk addresses this
issue by only showing errors that belong to that customer.