Title: api-docs: include explanation of the special character * for the If-Match header
Class: fix
Compatible: compat
Component: rest-api
Date: 1695723736
Edition: cre
Knowledge: doc
Level: 1
Version: 2.3.0b1
We recently made changes to make it possible to provide the following header
in rest-api requests
"If-Match": "*"
instead of providing a resource's ETag.
This werk adds a short explanation to the api-docs so that our users know
that this is possible.
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
Version: 2.1.0p34
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.
Title: apache_processes: we now replicate the configuration on remote sites
Class: fix
Compatible: compat
Component: wato
Date: 1695714746
Edition: cre
Knowledge: doc
Level: 1
Version: 2.3.0b1
This werk addresses an issue where we weren't replicating the configuration
for the number of apache processes. Now we do. On activate changes the
number of apache processes configured on the main site will now be replicated
on the remote site. An apache restart is required for these changes to
take effect.
Title: mssql_datafiles/transactionlogs: Regression in maximum size calculation
Class: fix
Compatible: compat
Component: checks
Date: 1694589964
Edition: cre
Knowledge: doc
Level: 1
Version: 2.3.0b1
This is a follow-up to Werk #14421.
Since Checkmk 2.1.0p5, we calculate the maximum size as the sum of available
and used size for unlimited instances.
However, in some cases, we accidentally drop explicit thresholds for the
maximum size if avaiable, falling back to the unlimited case.
Title: LDAP connection ids that are invalid user ids will no longer crash Checkmk
Class: fix
Compatible: compat
Component: wato
Date: 1686117166
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p11
LDAP connection names have have stricter requirements in Checkmk version 2.2.0.
Up until now, Checkmk did not check these requirements when creating new LDAP
connections nor did an update convert them to fit the new requirements.
This Werk tightens LDAP connection id validation to fit the new requirements.
Updating Checkmk will cause all spaces in connection ids to be replaced with
underscores, as this is the most common manifestation of this incompetability.
If you still are unable to update, please check if your connection id consist only
of letters and dashes, starting with a letter.
Title: nvidia_smi: Show Use full PCI bus ID
Class: fix
Compatible: incomp
Component: checks
Date: 1695304807
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p11
This change affects users of the following checks:
* nvidia_smi_memory_util
* nvidia_smi_gpu_util
* nvidia_smi_en_de_coder_util
* nvidia_smi_power
* nvidia_smi_temperature
Previously, the PCI bus ID of NVIDIA GPUs would be incorrectly removed. This caused GPUs to be
omitted, which should have been discovered. With this Werk, the full PCI bus ID is used as a service
item. Users must rediscover the services.
Title: nvidia_smi: Show Use full PCI bus ID
Class: fix
Compatible: incomp
Component: checks
Date: 1695304807
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p11
This change affects users of the following checks:
* nvidia_smi_memory_util
* nvidia_smi_gpu_util
* nvidia_smi_en_de_coder_util
* nvidia_smi_power
* nvidia_smi_temperature
Previously, the PCI bus ID of NVIDIA GPUs would be incorrectly removed. This caused GPUs to be
omitted, which should have been discovered. With this Werk, the full PCI bus ID is used as a service
item. Users must rediscover the services.
Werk 15772 was deleted. The following Werk is no longer relevant.
Title: checking: fix cache validity of piggyback sections
Class: fix
Compatible: compat
Component: checks
Date: 1694192952
Edition: cre
Knowledge: doc
Level: 1
Version: 2.1.0p34
Previously, piggyback sections had a cache validitiy of 90 seconds
if checking was called from Checkmk and (checking interval * 1.5)
seconds if called from the command line.
This led to services in piggyback hosts becoming stale if checking
interval of a source host was bigger than 1 minute.
Cache validity is now (checking interval * 1.5) in both cases.
Werk 16016 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: mk_postgres: addition of option to specify instance name
Class: fix
Compatible: incomp
Component: core
Date: 1690981131
Edition: cre
Knowledge: doc
Level: 1
Version: 2.1.0p33
The migration of the postgres_instances check plugin to the new CheckAPI broke the discovery
mechanism of the plugin as it previously allowed an instance to have no specified name. This
werk introduces the option to specify an explicit name for an instance. The mk_postgres plugin
is adjusted accordingly and raises an error if the name cannot be inferred from .env file. To
benefit from this change and also resolve the error, the user should adjust or bake the config
file again and roll out the newly adapted plugin. For manual adaptation, instance entries should
be adapted to have the following format:
<code>
INSTANCE=<instance env filepath>:<username>:<instance pgpass filepath>:<instance name (optional)>
</code>
where ':' (colon) is the respective separator character.
------------------------------------<diff>-------------------------------------------
Title: mk_postgres: addition of option to specify instance name
Class: fix
Compatible: incomp
Component: core
Date: 1690981131
Edition: cre
Knowledge: doc
Level: 1
Version: 2.1.0p33
The migration of the postgres_instances check plugin to the new CheckAPI broke the discovery
mechanism of the plugin as it previously allowed an instance to have no specified name. This
werk introduces the option to specify an explicit name for an instance. The mk_postgres plugin
is adjusted accordingly and raises an error if the name cannot be inferred from .env file. To
benefit from this change and also resolve the error, the user should adjust or bake the config
file again and roll out the newly adapted plugin. For manual adaptation, instance entries should
be adapted to have the following format:
<code>
- INSTANCE=<instance env filepath>:<username>:<instance pgpass filepath>:<instance name (optional)>
? ^ ^ ^ ^ ^ ^ ^ ^
+ INSTANCE=<instance env filepath>:<username>:<instance pgpass filepath>:<instance name (optional)>
? ^^^^ ^^^^ ^^^^ ^^^^ ^^^^ ^^^^ ^^^^ ^^^^
</code>
where ':' (colon) is the respective separator character.
Title: Fix import of iCalendar files
Class: fix
Compatible: compat
Component: wato
Date: 1695370450
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p11
The import of iCalendar files was broken in earlier 2.2 versions, resulting in
an error like “The file does not seem to be a valid iCalendar file.AAA“.