Title: mem_win: rename 'Commit Charge' to 'Virtual Memory' for correctness
Class: fix
Compatible: compat
Component: checks
Date: 1713530099
Edition: cre
Level: 1
Version: 2.2.0p26
The value previously displayed as 'Commit Charge' did not match its
description. Therefore, this value has been accurately renamed to
'Virtual Memory,' while maintaining the original calculation method.
Correspondingly, the titles of related graphs have been adjusted to
reflect this change.
In versions prior to 2.3, the service summary included a metric labeled
'Pagefile installed.' This has now been correctly renamed to
'Total Virtual Memory,' as it never accurately represented the
'Pagefile installed.'
Title: docker_container: skip on incomplete data for diskstat and memory
Class: fix
Compatible: compat
Component: checks
Date: 1713263300
Edition: cre
Level: 1
Version: 2.2.0p26
During the data parsing of a container, it is possible to encounter
incomplete metric sets, which previously caused a crash. Since the
data in these instances is simply unavailable, we now skip the
discovery or check cycle for such cases. This adjustment is applied
to docker container disktat and memory check plugins.
[//]: # (werk v2)
# Warn during update if contact groups are used in rulesets but not available
key | value
---------- | ---
date | 2024-04-23T07:42:11+00:00
version | 2.4.0b1
class | fix
edition | cme
component | wato
level | 1
compatible | yes
Some rulesets like 'Assignment of hosts (or services) to contact groups' use
contact groups which may not be synced because they are assigned to a specific
customer or to 'Provider' (default). This inconsistency might have already been
present in your configuration but went unnoticed in the previous versions. With
2.3, we introduced new validation mechanics which now warn you about this
potential issue.
With this change we make the shown error message a more helpful so that users
get a hint how to solve the situation.
[//]: # (werk v2)
# host_config: introduce include_links option for Show all hosts endpoint
key | value
---------- | ---
date | 2024-04-23T06:37:18+00:00
version | 2.4.0b1
class | feature
edition | cre
component | rest-api
level | 1
compatible | no
This werk introduces the flag 'include_links' for the 'Show all hosts'
host config endpoint. It toggles whether the links field should be populated
of the individual hosts. This serves as a mechanism to reduce the payload
generated. This field defaults to False and existing scripts therefore have
to be adjusted accordingly.
[//]: # (werk v2)
# Ruleset API: Fix error during AgentConfig creation
key | value
---------- | ---
date | 2024-04-19T11:48:42+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
When creating an `AgentConfig` rulespec using the Ruleset API an error
```
KeyError: 'cmk-match-type'
```
was raised.
[//]: # (werk v2)
# mem_win: rename 'Commit Charge' to 'Virtual Memory' for correctness
key | value
---------- | ---
date | 2024-04-19T12:34:59+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The value previously displayed as 'Commit Charge' did not match its
description. Therefore, this value has been accurately renamed to
'Virtual Memory,' while maintaining the original calculation method.
Correspondingly, the titles of related graphs have been adjusted to
reflect this change.
In versions prior to 2.3, the service summary included a metric labeled
'Pagefile installed.' This has now been correctly renamed to
'Total Virtual Memory,' as it never accurately represented the
'Pagefile installed.'
[//]: # (werk v2)
# docker_container: skip on incomplete data for diskstat and memory
key | value
---------- | ---
date | 2024-04-16T10:28:20+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
During the data parsing of a container, it is possible to encounter
incomplete metric sets, which previously caused a crash. Since the
data in these instances is simply unavailable, we now skip the
discovery or check cycle for such cases. This adjustment is applied
to docker container disktat and memory check plugins.
Werk 16237 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Path to mysql.ini under Windows for mk_sql
Class: fix
Compatible: compat
Component: checks
Date: 1708687568
Edition: cre
Level: 1
Version: 2.1.0p43
If you've been using mysql and the corresponding agent plugin <em>mk_sql</em>
under Windows, the plugin may have crashed and the agent output would then
show the following error:
C+:
<<<mysql_ping>>>
[[MySQL83]]
mysqladmin: File '\etc\check_mk\mysql.local.ini' not found (OS errno 2 - No such file or directory)
mysqladmin: [ERROR] Stopped processing the 'include' directive in file C:\ProgramData\checkmk\agent\config\mysql.ini at line 8.
C-:
Under Windows, the plugin config path <code>C:\ProgramData\checkmk\agent\config</code> is now used.
In contrast to the corresponding Linux plugin <code>mk_mysql</code>, the config path under Windows cannot be changed.
------------------------------------<diff>-------------------------------------------
Title: Path to mysql.ini under Windows for mk_sql
Class: fix
Compatible: compat
Component: checks
Date: 1708687568
Edition: cre
Level: 1
- Version: 2.1.0p42
? ^
+ Version: 2.1.0p43
? ^
If you've been using mysql and the corresponding agent plugin <em>mk_sql</em>
under Windows, the plugin may have crashed and the agent output would then
show the following error:
C+:
<<<mysql_ping>>>
[[MySQL83]]
mysqladmin: File '\etc\check_mk\mysql.local.ini' not found (OS errno 2 - No such file or directory)
mysqladmin: [ERROR] Stopped processing the 'include' directive in file C:\ProgramData\checkmk\agent\config\mysql.ini at line 8.
C-:
Under Windows, the plugin config path <code>C:\ProgramData\checkmk\agent\config</code> is now used.
In contrast to the corresponding Linux plugin <code>mk_mysql</code>, the config path under Windows cannot be changed.
Werk 16238 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Add m7i.large as aws resource type
Class: feature
Compatible: compat
Component: checks
Date: 1709038229
Edition: cre
Level: 1
Version: 2.1.0p43
You're affected if your aws_ec2_limits check reported "Unknown resource" and you're using "m7i.large".
The aws resource names are changing from time to time and we will need to find a more stable solution for that in the future.
But for now, this will be fixed by adding the resource name "m7i.large" to our internal list of aws resources.
------------------------------------<diff>-------------------------------------------
Title: Add m7i.large as aws resource type
Class: feature
Compatible: compat
Component: checks
Date: 1709038229
Edition: cre
Level: 1
- Version: 2.1.0p42
? ^
+ Version: 2.1.0p43
? ^
You're affected if your aws_ec2_limits check reported "Unknown resource" and you're using "m7i.large".
The aws resource names are changing from time to time and we will need to find a more stable solution for that in the future.
But for now, this will be fixed by adding the resource name "m7i.large" to our internal list of aws resources.