Title: windows_tasks: Display Correct Scheduled Task State
Class: fix
Compatible: incomp
Component: checks
Date: 1705315505
Edition: cre
Knowledge: doc
Level: 1
Version: 2.2.0p21
Previously, the `Scheduled Task State` could be N\A, if the Action of a Windows
task contained a comma. Moreover, the plugin only supported German or English
localization settings for Windows. Finally, with German localization settings
disabled scheduled tasks would be discovered (despite what the checkman page
claimed). This worked correctly with English localization settings. With this
Werk, `windows_tasks` uses the new PowerShell API to obtain the data. This
fixes the aforementioned issues.
Users, whom desire to discover disabled tasks need to configure the new service
discovery rule `Windows Tasks`.
The changes in this Werk are only applicable, if the underlying Windows version
supports the PowerShell API. The Windows versions supported by Checkmk 2.2.0 and
later all support the required the PowerShell functions. Versions such as
Windows 7 does not support the PowerShell API.
[//]: # (werk v2)
# host: query on mk_inventory no longer causing crash
key | value
---------- | ---
date | 2024-01-24T09:17:52+00:00
version | 2.3.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
Previously, when you had a host that had no check running,
calling the following endpoint would cause a crash.
GET /domain-type/host/collections/all?columns=mkinventory
This werk addresses this issue by preventing the crash
and now returns an appropriate response.
[//]: # (werk v2)
# mk_redis: Use REDISCLI_AUTH instead of -a argument in order to hide password
key | value
---------- | ---
date | 2024-01-24T09:23:40+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
mk_redis used to expose the password in the process name because of the '-a' argument.
This has been fixed using the environment variable REDISCLI_AUTH.
Werk 15649 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: windows_tasks: Display Correct Scheduled Task State
Class: fix
Compatible: incomp
Component: checks
Date: 1705315505
Edition: cre
Knowledge: doc
Level: 1
Version: 2.3.0b1
Previously, the `Scheduled Task State` could be N\A, if the Action of a Windows
task contained a comma. Moreover, the plugin only supported German or English
localization settings for Windows. Finally, with German localization settings
disabled scheduled tasks would be discovered (despite what the checkman page
claimed). This worked correctly with English localization settings. With this
Werk, `windows_tasks` uses the new PowerShell API to obtain the data. This
fixes the aforementioned issues.
Users, whom desire to discover disabled tasks need to configure the new service
discovery rule `Windows Tasks`.
The changes in this Werk are only applicable, if the underlying Windows version
supports the PowerShell API. The Windows versions supported by Checkmk 2.2.0 and
later all support the required the PowerShell functions. Versions such as
Windows 7 does not support the PowerShell API.
------------------------------------<diff>-------------------------------------------
Title: windows_tasks: Display Correct Scheduled Task State
Class: fix
- Compatible: compat
? --
+ Compatible: incomp
? ++
Component: checks
Date: 1705315505
Edition: cre
Knowledge: doc
Level: 1
Version: 2.3.0b1
Previously, the `Scheduled Task State` could be N\A, if the Action of a Windows
task contained a comma. Moreover, the plugin only supported German or English
- localization settings for Windows. With this Werk, `windows_tasks` uses the
- new PowerShell API to obtain the data. This fixes the aforementioned issues.
+ localization settings for Windows. Finally, with German localization settings
+ disabled scheduled tasks would be discovered (despite what the checkman page
+ claimed). This worked correctly with English localization settings. With this
+ Werk, `windows_tasks` uses the new PowerShell API to obtain the data. This
+ fixes the aforementioned issues.
+
+ Users, whom desire to discover disabled tasks need to configure the new service
+ discovery rule `Windows Tasks`.
The changes in this Werk are only applicable, if the underlying Windows version
supports the PowerShell API. The Windows versions supported by Checkmk 2.2.0 and
- later all have the required the PowerShell functionality. Windows 7 does not
- meet the requirements.
+ later all support the required the PowerShell functions. Versions such as
+ Windows 7 does not support the PowerShell API.
[//]: # (werk v2)
# mk_jolokia: Respect Timeout Settings
key | value
---------- | ---
date | 2024-01-23T09:28:00+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Previously, passing a timeout parameter the agent plugin `mk_jolokia` had no effect.
This has been fixed.
[//]: # (werk v2)
# special_zerto: Error Message in Check_MK HW/SW Inventory
key | value
---------- | ---
date | 2024-01-23T08:14:35+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Previously, the agent special_zerto would show the following error message in the Check_MK HW/SW
Inventory
```
NOOPParser: Ignoring invalid data b'<<<zerto_agent:sep(0)>>>Initialized OK<<<<host1.example.com>>>>
```
Moreover, the service `Zerto Agent Status` was not discoverable and some piggyback data would
incorrectly be mapped to the source host. This is now fixed.
Werk 16287 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: rule_notification: match_hosttag now accepts custom tag ids
Class: fix
Compatible: incomp
Component: rest-api
Date: 1705077038
Edition: cre
Level: 1
Version: 2.2.0p21
Previously, when creating or updating a notification rule,
the match_host_tag field would only allow for builtin tag ids.
With this werk we now accept any configured host tag id.
The schema has also changed in order to make this possible.
This means that instead of a field representing each tag,
you now have to pass a list of aux tag ids/tag group tag ids
along with an operator. This way we can determine if the
tag id should match or not.
e.g.
C+:
{
"match_host_tags": {
"state": "enabled",
"value": [
{
"tag_type": "aux_tag",
"tag_id": "snmp",
"operator": "is_set",
},
{
"tag_type": "tag_group",
"tag_group_id": "criticality",
"operator": "is",
"tag_id": "prod",
},
{
"tag_type": "tag_group",
"tag_group_id": "networking",
"operator": "is_not",
"tag_id": "lan",
}
],
},
}
C-:
------------------------------------<diff>-------------------------------------------
Title: rule_notification: match_hosttag now accepts custom tag ids
Class: fix
Compatible: incomp
Component: rest-api
Date: 1705077038
Edition: cre
Level: 1
- Version: 2.2.0p20
? ^
+ Version: 2.2.0p21
? ^
Previously, when creating or updating a notification rule,
the match_host_tag field would only allow for builtin tag ids.
With this werk we now accept any configured host tag id.
The schema has also changed in order to make this possible.
This means that instead of a field representing each tag,
you now have to pass a list of aux tag ids/tag group tag ids
along with an operator. This way we can determine if the
tag id should match or not.
e.g.
C+:
{
"match_host_tags": {
"state": "enabled",
"value": [
{
"tag_type": "aux_tag",
"tag_id": "snmp",
"operator": "is_set",
},
{
"tag_type": "tag_group",
"tag_group_id": "criticality",
"operator": "is",
"tag_id": "prod",
},
{
"tag_type": "tag_group",
"tag_group_id": "networking",
"operator": "is_not",
"tag_id": "lan",
}
],
},
}
C-: