[//]: # (werk v2)
# pandacom_psu: New PSU types added
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-01-04T13:07:52+00:00
level | 1
class | fix
component | checks
edition | cre
Pandacom devices with PSU types 65025-65033 caused a crash during
section parsing.
Now, Checkmk recognizes the new type codes and reports the correct
PSU type.
Title: mssql_backup: fix 'no backup found' for case-insensitive databases
Class: fix
Compatible: compat
Component: checks
Date: 1702370026
Edition: cre
Level: 1
Version: 2.3.0b1
In certain circumstances it was possible that the `mssql.vbs` agent plugin
returned `no backup found` because it could not map the found backup to the
database.
The reason for that was, that the comparison between the backups database name
and the database name was case sensitive, but its possible to configure mssql
in a way that backups database name and database name does not match case
sensitive.
We now compare both names on the mssql server so the configured case
sensitivity is respected.
Title: veeam_cdp_jobs: Handle last sync time from the future
Class: fix
Compatible: compat
Component: checks
Date: 1703838299
Edition: cre
Level: 1
Version: 2.1.0p38
Previously, the veeam_cdp_jobs would crash when receiving last
sync time from the future with a message:
C+:
raise ValueError("Cannot render negative timespan")
C-:
Now, the time since the last job run will be 0 for such cases.
Title: mk_oracle: restore compatibility with oracle 12c
Class: fix
Compatible: compat
Component: agents
Date: 1698138075
Edition: cre
Knowledge: doc
Level: 1
Version: 2.2.0p18
<a href="https://checkmk.com/werk/14839">Werk #14839</a> added the function
<tt>listagg</tt> to one of our queries.
Older versions of oracle database expect a <tt>WITHIN</tt> statement after the
<tt>listagg</tt> function. This was added to assure compatibility with older
databases.
Title: mk_oracle.ps1: port changes made in werk 14839 to windows agent plugin
Class: fix
Compatible: incomp
Component: agents
Date: 1698137301
Edition: cre
Knowledge: doc
Level: 1
Version: 2.2.0p18
Changes made in <a href="https://checkmk.com/werk/14839">Werk #14839</a> where
only applied to the linux agent plugin of mk_oracle. Now those changes are also
applied to mk_oracle.ps1
Title: veeam_cdp_jobs: Handle last sync time from the future
Class: fix
Compatible: compat
Component: checks
Date: 1703838299
Edition: cre
Level: 1
Version: 2.2.0p18
Previously, the veeam_cdp_jobs would crash when receiving last
sync time from the future with a message:
C+:
raise ValueError("Cannot render negative timespan")
C-:
Now, the time since the last job run will be 0 for such cases.
[//]: # (werk v2)
# mk_oracle: restore compatibility with oracle 12c
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2023-10-24T09:01:15+00:00
level | 1
class | fix
component | agents
edition | cre
<a href="https://checkmk.com/werk/14839">Werk #14839</a> added the function
<tt>listagg</tt> to one of our queries.
Older versions of oracle database expect a <tt>WITHIN</tt> statement after the
<tt>listagg</tt> function. This was added to assure compatibility with older
databases.
[//]: # (werk v2)
# mk_oracle.ps1: port changes made in werk 14839 to windows agent plugin
key | value
---------- | ---
compatible | no
version | 2.3.0b1
date | 2023-10-24T08:48:21+00:00
level | 1
class | fix
component | agents
edition | cre
Changes made in <a href="https://checkmk.com/werk/14839">Werk #14839</a> where
only applied to the linux agent plugin of mk_oracle. Now those changes are also
applied to mk_oracle.ps1
[//]: # (werk v2)
# veeam_cdp_jobs: Handle last sync time from the future
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2023-12-29T08:24:59+00:00
level | 1
class | fix
component | checks
edition | cre
Previously, the veeam_cdp_jobs would crash when receiving last
sync time from the future with a message:
```
raise ValueError("Cannot render negative timespan")
```
Now, the time since the last job run will be 0 for such cases.
[//]: # (werk v2)
# Split up rule "Mails in outgoing mail queue"
key | value
---------- | ---
date | 2023-12-25T17:11:32+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
This affects all users that had rules for "Mails in outgoing mail queue" configured.
To clean up inconsistencies that the new APIs no longer tolerate, we had to split the ruleset into two.
We renamed "Mails in outgoing mail queue" to "Mails in outgoing mail queue (multiple queues)" and added a new ruleset "Mails in outgoing mail queue (single queue)".
The required new rules are created automatically during upgrade, but we advise users to check if they have rules that are not needed anymore.
The plugins using the new ruleset are
* Barracuda SPAM Firewall: Active and Deferred Mail Queue Length (`barracuda_mailqueues`)
* Nullmailer: Mailqueue Length (`nullmailer_mailq`)
* qmail: Mailqueue Length (`qmail_stats`)