Title: Redesign of audit log page
Class: feature
Compatible: compat
Component: multisite
Date: 1699865170
Edition: cre
Level: 1
Version: 2.3.0b1
Werk #16072 introduced the regulare rotating of the wato audit log.
The audit log page was now adjusted to also show archived/rotated logs.
Therefore, you are now asked to choose a file to view instead of showing the current log
on opening the page.
Besides that, the "Clear" option was renamed to "Archive" because the current
log file is archived not cleared.
Title: Add wato audit log to logrotate cronjob
Class: fix
Compatible: incomp
Component: omd
Date: 1699864221
Edition: cre
Level: 1
Version: 2.3.0b1
The wato audit log ~/var/check_mk/wato/log/wato_audit.log was not rotated
regularly. This lead to an ever growing audit log, which could not be viewed
anymore once it reached several hundred MB of log lines.
Therefore, the audit log will now rotate regularly to archive files bigger than
300MB.
Existing logfiles greater 300MB will be splitted up on update and the source
file will be backed up as wato_audit.log_backup.
Title: netapp_api_luns: Add vserver and volume name
Class: feature
Compatible: compat
Component: checks
Date: 1698062759
Edition: cre
Level: 1
Version: 2.3.0b1
If you have a Setup with Multiple Netapps and Thousands of Luns, it was not
possible to figure out to where a Lun belongs.
With this Werk, this information is now part of the service output.
Title: "Always up" hosts can always notify
Class: fix
Compatible: compat
Component: core
Date: 1699884551
Edition: cee
Level: 1
Version: 2.3.0b1
Do not postpone notifications for "always up" hosts.
The notification logic would wrongly assume that "always up" hosts may,
in fact, be down and erroneously postpone notifications. This has been
fixed, such hosts are never down.
Title: downtimes: can now delete downtimes from remote sites
Class: fix
Compatible: compat
Component: rest-api
Date: 1699869696
Edition: cre
Level: 1
Version: 2.3.0b1
As a result a previous change to the downtimes delete endpoint,
we introduced a bug which prevented downtime deletion on
remote sites.
This werk addresses this issue. Downtimes on remote sites are now
deleted as expected.
Title: jolokia_metrics_app_sess: incorrectly applied lower levels
Class: fix
Compatible: incomp
Component: checks
Date: 1699617831
Edition: cre
Level: 1
Version: 2.3.0b1
The plugin <i>Java Virtual Machine: Number of Sessions</i> (<tt>jolokia_metrics_app_sess</tt>) applied the configured levels incorrectly.
This werk is only incompatible for users that adjusted there configuration to compensate this bug.
If this is the case for you, please adjust your "lower levels" in the ruleset <i>JVM session count</i>.
Title: Notification spooler: Fix ignored timing settings for specific methods
Class: fix
Compatible: incomp
Component: notifications
Date: 1699356565
Edition: cee
Level: 1
Version: 2.3.0b1
If you used notification spooling and configured "Timing settings for specific
methods" in the global settings option "Notification Spooler Configuration",
the settings "Maximum number of delivery attempts" and "Timeout" had no effect.
The notification methods were executed until they succeded.
Please note:
This change can cause changes in the notification spooling, please check if the
behaviour still matches your needs. Otherwise you would have to adjust the
mentioned settings again.
Werk 15302 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: dell_poweredge_status: crash on unknown state
Class: fix
Compatible: compat
Component: checks
Date: 1698738832
Edition: cre
Level: 1
Version: 2.3.0b1
If the device returned an unknown state for <tt>globalSystemStatus</tt>
dell_poweredge_status crashed with error <tt>ValueError: not enough values to
unpack (expected 2, got 1)</tt>.
The new behavior is, that the service will be cirital and report <tt>unknown
state</tt> as system status.
------------------------------------<diff>-------------------------------------------
Title: dell_poweredge_status: crash on unknown state
Class: fix
Compatible: compat
Component: checks
Date: 1698738832
Edition: cre
Level: 1
Version: 2.3.0b1
- If the device returned an unknown state for
+ If the device returned an unknown state for <tt>globalSystemStatus</tt>
? +++++++++++++++++++++++++++
+ dell_poweredge_status crashed with error <tt>ValueError: not enough values to
+ unpack (expected 2, got 1)</tt>.
- The new behavior is, that the service will be cirital and report
+ The new behavior is, that the service will be cirital and report <tt>unknown
? +++++++++++
+ state</tt> as system status.
Title: prism_vm_tools: tools state and enable state can now be ignored
Class: feature
Compatible: compat
Component: checks
Date: 1698910390
Edition: cre
Level: 1
Version: 2.3.0b1
Dropdowns "Tools install state" and "VMTools activation state" of rule "Nutanix
Prism VM Tools" not contain the option "ignored".