Title: oracle_instances: Fixed parsing of section with failure and additional information
Class: fix
Compatible: compat
Component: checks
Date: 1694187291
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.3.0b1
Sometimes when an oracle instance has a failure it deliveres some additional information. This information caused the failure of the section parsing.
The section in the agent output looks something like this:
C+:
<<<oracle_instance:sep(124)>>>
+ASM|FAILURE|ERROR: ORA-12541: ...
NAME DATABASE_ROLE OPEN_MODE DB_UNIQUE_NAME FLASHBACK_ON FORCE_LOGGING SWITCHOVER_STATUS
C-:
This has now been fixed and the additional information should not cause any problems.
Title: notification rules: match_folder value now matches correctly to available folders
Class: fix
Compatible: incomp
Component: rest-api
Date: 1694514118
Edition: cre
Knowledge: doc
Level: 1
Version: 2.3.0b1
This werk addresses an issue when creating or updating a notification rule
via the REST-API. Previously, it would not correctly match the desired folder
and as a result, you had to set this option to disabled which meant all rules
were created in the main folder only.
Now the match_folder value field should match a folder id, in the form of the
folder path, replacing / for ~
E.g.
/folder1 -> ~folder1
/folder1/folder2 -> ~folder1~folder2
Title: mssql_backup: Now mssql_backup finds backup even if collation is case sensitive
Class: fix
Compatible: compat
Component: checks
Date: 1694612939
Edition: cre
Knowledge: doc
Level: 1
Version: 2.2.0p10
Previously, if the collation was case sensitive some of the backup were not found.
This has now been fixed and the backups will be found regardless of case sensitivity.
Title: oracle_instances: Fixed parsing of section with failure and additional information
Class: fix
Compatible: compat
Component: checks
Date: 1694187291
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p10
Sometimes when an oracle instance has a failure it deliveres some additional information. This information caused the failure of the section parsing.
The section in the agent output looks something like this:
C+:
<<<oracle_instance:sep(124)>>>
+ASM|FAILURE|ERROR: ORA-12541: ...
NAME DATABASE_ROLE OPEN_MODE DB_UNIQUE_NAME FLASHBACK_ON FORCE_LOGGING SWITCHOVER_STATUS
C-:
This has now been fixed and the additional information should not cause any problems.
ID: 15834
Title: Open Hardware monitor is updated to the version 0.9.6
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.1.0p34
Older versions of Open hardware monitor isn't compatible
with Windows 11 and have quite limited support for new
hardware.
With this release the problem has been eliminated.
ID: 16097
Title: hosts: fix permission checking for moving hosts to other folders
Component: REST API
Level: 1
Class: Bug fix
Version: 2.3.0b1
This werk fixes an issue that was introduced recently with regards to
moving hosts to other folders. Permission checking was mistakingly
carried out by checking for the correct contact groups on the host,
source folder and target folder. This is no longer the case.
ID: 15641
Title: Prometheus: Properly Encode PromQL Queries
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0p10
The Prometheus agent allows specifying PromQL queries via the option <tt>Service creation using
PromQL queries</tt>. In 2.2.0, any query containing a '+' would not be encoded properly. For
example, the query
C+:
up{container=".+"}
C-:
would result in a HTTP request, which is interpreted by Prometheus as
C+:
up{container=". "}
C-:
ID: 16056
Title: Fix error on showing open bulk notifications
Component: Notifications
Level: 1
Class: Bug fix
Version: 2.2.0p10
If the option "Show bulks" was used on the notification configuration page, an
error like "Internal error: could not convert string to float 'n.a.'" could
occur.
ID: 15772
Title: checking: fix cache validity of piggyback sections
Component: Checks & agents
Level: 1
Class: Bug fix
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.