Title: azure_vault: Fix last backup status "Healthy" mislabeled as critical status
Class: fix
Compatible: compat
Component: checks
Date: 1696592659
Edition: cce
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p12
The Azure/Recovery Services Vault service currently classifies a "Healthy" last backup status incorrectly and will become critical because of it.
This has been fixed with this werk.
Title: azure_vault: Fix last backup status "Healthy" mislabeled as critical status
Class: fix
Compatible: compat
Component: checks
Date: 1696592659
Edition: cce
Knowledge: doc
Level: 1
Version: 2.3.0b1
The Azure/Recovery Services Vault service currently classifies a "Healthy" last backup status incorrectly and will become critical because of it.
This has been fixed with this werk.
Title: event console: Incorrect title and link to the event console
Class: fix
Compatible: compat
Component: ec
Date: 1696513660
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.1.0p35
This Werk fixes the generation of the title and the link to access the event console when the responsible command has more than one argument.
Title: rule: update a rule preserving its index, folder, and ruleset
Class: feature
Compatible: compat
Component: rest-api
Date: 1694014829
Edition: cre
Knowledge: undoc
Level: 1
State: unknown
Version: 2.1.0p35
This werk enables the user to update a rule using the REST API. Updating a rule preserves its index, folder, and ruleset.
Title: Add max_long_output_size livestatus column
Class: feature
Compatible: compat
Component: livestatus
Date: 1696505149
Edition: cee
Knowledge: undoc
Level: 1
State: unknown
Version: 2.1.0p35
The "max_long_output_size" in the status table returns the
value that is currently configured.
For Nagios, the column always returns 0 as Nagios doesn't
support this feature.
Title: Refer to a time period by its name instead of its alias in the REST API
Class: fix
Compatible: incomp
Component: rest-api
Date: 1696245234
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.1.0p35
Before this Werk, a time period to be excluded was referred to by its alias and not its name. This Werk changes that behaviour and now time periods to exclude must be referred to by their name.
Also, the retrieval of a time period now returns time periods names in the exclude field. To integrate this change, the user must fill in the exclude field with the name of the time periods instead of their alias.
Affected endpoints
* creation
* update
* retrieval
Title: event console: Incorrect title and link to the event console
Class: fix
Compatible: compat
Component: ec
Date: 1696513660
Edition: cre
Knowledge: doc
Level: 1
Version: 2.2.0p12
This Werk fixes the generation of the title and the link to access the event console when the responsible command has more than one argument.
Werk 15774 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: checking: Prevent data loss on hosts with longer check intervals
Class: fix
Compatible: compat
Component: core
Date: 1695217743
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p12
Previously, the validity of agent data for discovery and HW/SW inventory checks was 2 minutes.
When checking is performed with a longer interval, the discovery would re-trigger fetching of the agent data.
In some checks this leads to data loss, because the checking fetches the data again and the data
fetched by the discovery is lost.
The cache interval for discovery and HW/SW inventory checks is now 1.5 * checking interval.
------------------------------------<diff>-------------------------------------------
Title: checking: Prevent data loss on hosts with longer check intervals
Class: fix
Compatible: compat
Component: core
Date: 1695217743
Edition: cre
Knowledge: doc
Level: 1
State: unknown
- Version: 2.2.0p11
? ^
+ Version: 2.2.0p12
? ^
Previously, the validity of agent data for discovery and HW/SW inventory checks was 2 minutes.
When checking is performed with a longer interval, the discovery would re-trigger fetching of the agent data.
In some checks this leads to data loss, because the checking fetches the data again and the data
fetched by the discovery is lost.
The cache interval for discovery and HW/SW inventory checks is now 1.5 * checking interval.
Werk 16161 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: discovery: Fix missing datasource error for cluster hosts
Class: fix
Compatible: compat
Component: checks
Date: 1696495573
Edition: cre
Knowledge: doc
Level: 1
Version: 2.2.0p12
Previously, a missing datasource error would be shown in a discovery
page of a cluster host if the cluster host had 'No IP' configured
but had nodes with an agent datasource.
Services of a cluster host would also become vanished.
Checkmk now supports the described setup, there is no error in the
discovery page and clustered services are discovered.
------------------------------------<diff>-------------------------------------------
Title: discovery: Fix missing datasource error for cluster hosts
Class: fix
Compatible: compat
Component: checks
Date: 1696495573
Edition: cre
Knowledge: doc
Level: 1
- Version: 2.2.0p11
? ^
+ Version: 2.2.0p12
? ^
Previously, a missing datasource error would be shown in a discovery
page of a cluster host if the cluster host had 'No IP' configured
but had nodes with an agent datasource.
Services of a cluster host would also become vanished.
Checkmk now supports the described setup, there is no error in the
discovery page and clustered services are discovered.
Title: discovery: Fix missing datasource error for cluster hosts
Class: fix
Compatible: compat
Component: checks
Date: 1696495573
Edition: cre
Knowledge: doc
Level: 1
Version: 2.2.0p11
Previously, a missing datasource error would be shown in a discovery
page of a cluster host if the cluster host had 'No IP' configured
but had nodes with an agent datasource.
Services of a cluster host would also become vanished.
Checkmk now supports the described setup, there is no error in the
discovery page and clustered services are discovered.