[//]: # (werk v2)
# Fix crash in filesystem related Nutanix services
key | value
---------- | ---
date | 2024-03-18T09:17:45+00:00
version | 2.3.0b3
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This Werk fixes a crash in the Nutanix "NTNX Storage", "Storage Pool"
and "Container" services.
It also adds the option to update the naming of the "Prism Alerts",
"Prism Cluster", "Container" and "Storage Pool" services to be more consistent
with the other Nutanix services. The new names will be automatically used in new
installations.
[//]: # (werk v2)
# postfix: Fix Postfix status monitoring for agents run in Docker
key | value
---------- | ---
compatible | yes
version | 2.3.0b3
date | 2024-03-13T09:57:01+00:00
level | 1
class | fix
component | checks
edition | cre
Previously, Checkmk agent used the data from /proc to determine if Postfix instance is running.
Since docker containers don't have permissions to read /proc, the agent always reported
the Postfix instance as 'not running'.
This resulted in CRIT 'Postfix status' service even if Postfix instance was running correctly.
[//]: # (werk v2)
# add labels for Nutanix
key | value
---------- | ---
date | 2024-03-14T10:03:01+00:00
version | 2.3.0b3
class | feature
edition | cre
component | checks
level | 1
compatible | yes
This werk adds the following labels:
For the host with the Nutanix special agent:
* cmk/nutanix/object:control_plane
For Nutanix hosts:
* cmk/nutanix/object:node
* cmk/os_platform:nutanix
* cmk/os_name:Nutanix AHV
For Nutanix VMs:
* cmk/nutanix/object:vm
[//]: # (werk v2)
# bi_aggregation: Better visualization of aggregation errors
key | value
---------- | ---
date | 2024-03-15T15:27:21+00:00
version | 2.3.0b3
class | feature
edition | cre
component | checks
level | 1
compatible | yes
Aggregation errors are shown in the details of 'Aggr' services.
Previously, all aggregation errors were shown in the same tree
independent of whether they influence the state of the service or not,
which lead to confusion.
Now, two trees are shown, 'Aggregation problems affecting the state' and
'Aggregation problems not affecting the state'.
Werk 16382 was deleted. The following Werk is no longer relevant.
[//]: # (werk v2)
# Cleanup SNMP version and bulkwalk rulesets
key | value
---------- | ---
date | 2024-03-13T06:09:17+00:00
version | 2.3.0b3
class | fix
edition | cre
component | wato
level | 1
compatible | no
This werk is incompatible for users using the rule previously named "Disable bulk walks on SNMPv2c/v3" (see below for details).
The ruleset for disabling bulkwalks has not been correctly applied to SNMPv3 hosts using the inline backend in the past.
In addition it has been interfering with the ruleset to enable SNMP version 2 (over version 1).
## Change
The following new ruleset _names_ are introduced:
* "Disable bulkwalks" (formerly known as "Disable bulk walks on SNMPv2c/v3")
* "Enable SNMPv2c for hosts" (formerly known as "Enable SNMPv2c and bulk walk for hosts")
* "Enable SNMPv2c for management boards" (formerly known as "Enable SNMPv2c and bulk walk for management boards")
With this change the following logic applies:
* **bulkwalk**:
The "bulkwalk" query is used if and only if the ruleset "Disable bulkwalks" does not match the host and it is available in the used SNMP version (v1 does not have "bulkwalk").
* **SNMP version**:
Checkmk will use SNMP v3 if and only if the host configuration contains SNMP v3 style credentials.
The remaining hosts will use SNMP v2c if and only if the ruleset "Enable SNMPv2c for hosts" matches, otherwise SNMPv1.
This applies to both the "inline" and the "classic" backend.
## Incompatibility
Previously, in order to succesfully disable SNMP bulkwalks, users had to make sure the "Disable bulk walks on SNMPv2c/v3" matched the host, and the "Enable SNMPv2c and bulk walk for hosts" did not match the host.
This is no longer the case.
All hosts that are neither configured for SNMPv3 (see above) nor matched by the "Enable SNMPv2c" ruleset will use SNMPv1.
[//]: # (werk v2)
# folders: Fix folders with same title were not displayed
key | value
---------- | ---
date | 2024-03-14T13:43:44+00:00
version | 2.3.0b3
class | fix
edition | cre
component | wato
level | 1
compatible | yes
Before this Werk, when subfolders were listed and some of them had the
same title, only the last one of the group was displayed. This Werk
fixes that problem and now all folders are displayed.
[//]: # (werk v2)
# Cleanup SNMP version and bulkwalk rulesets
key | value
---------- | ---
date | 2024-03-13T06:09:17+00:00
version | 2.3.0b3
class | fix
edition | cre
component | wato
level | 1
compatible | no
This werk is incompatible for users using the rule previously named "Disable bulk walks on SNMPv2c/v3" (see below for details).
The ruleset for disabling bulkwalks has not been correctly applied to SNMPv3 hosts using the inline backend in the past.
In addition it has been interfering with the ruleset to enable SNMP version 2 (over version 1).
## Change
The following new ruleset _names_ are introduced:
* "Disable bulkwalks" (formerly known as "Disable bulk walks on SNMPv2c/v3")
* "Enable SNMPv2c for hosts" (formerly known as "Enable SNMPv2c and bulk walk for hosts")
* "Enable SNMPv2c for management boards" (formerly known as "Enable SNMPv2c and bulk walk for management boards")
With this change the following logic applies:
* **bulkwalk**:
The "bulkwalk" query is used if and only if the ruleset "Disable bulkwalks" does not match the host and it is available in the used SNMP version (v1 does not have "bulkwalk").
* **SNMP version**:
Checkmk will use SNMP v3 if and only if the host configuration contains SNMP v3 style credentials.
The remaining hosts will use SNMP v2c if and only if the ruleset "Enable SNMPv2c for hosts" matches, otherwise SNMPv1.
This applies to both the "inline" and the "classic" backend.
## Incompatibility
Previously, in order to succesfully disable SNMP bulkwalks, users had to make sure the "Disable bulk walks on SNMPv2c/v3" matched the host, and the "Enable SNMPv2c and bulk walk for hosts" did not match the host.
This is no longer the case.
All hosts that are neither configured for SNMPv3 (see above) nor matched by the "Enable SNMPv2c" ruleset will use SNMPv1.
Werk 16619 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Ruleset API: Ruleset validation
key | value
---------- | ---
date | 2024-03-11T12:46:16+00:00
version | 2.3.0b3
class | fix
edition | cre
component | checks
level | 1
compatible | no
Rulespec/ruleset names now have to be valid [python identifiers](https://docs.python.org/3/reference/lexical_analysis.html#iden….
The validation occurs during instantiation and will raise a `ValueError` when a violation is found.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Ruleset API: Ruleset validation
key | value
---------- | ---
date | 2024-03-11T12:46:16+00:00
version | 2.3.0b3
class | fix
edition | cre
component | checks
level | 1
compatible | no
Rulespec/ruleset names now have to be valid [python identifiers](https://docs.python.org/3/reference/lexical_analysis.html#iden….
The validation occurs during instantiation and will raise a `ValueError` when a violation is found.
-
[//]: # (werk v2)
# Ruleset API: Ruleset validation
key | value
---------- | ---
date | 2024-03-11T12:46:16+00:00
version | 2.3.0b3
class | fix
edition | cre
component | checks
level | 1
compatible | no
Rulespec/ruleset names now have to be valid [python identifiers](https://docs.python.org/3/reference/lexical_analysis.html#iden….
The validation occurs during instantiation and will raise a `ValueError` when a violation is found.