[//]: # (werk v2)
# SLA alert levels: show CRIT state if SLA alerts levels are CRIT but SLA not broken yet
key | value
---------- | ---
date | 2024-08-30T10:07:12+00:00
version | 2.4.0b1
class | fix
edition | cee
component | multisite
level | 1
compatible | yes
When configuring SLA alerts levels only the WARN state was shown in a view,
in case the alert levels for warning have been reached.
The CRIT alerts levels were shown as OK as long as the SLA was not broken.
Now this already shows up as CRIT, even though the SLA is not yet broken.
[//]: # (werk v2)
# Support Diagnostics: Fix data collected about the CPU
key | value
---------- | ---
date | 2024-08-30T07:56:06+00:00
version | 2.4.0b1
class | fix
edition | cre
component | wato
level | 1
compatible | yes
Prior to this werk, the information collected about the number of CPUs
was missing. Only the number of logical processors and CPU cores was
included. This is now fixed.
Werk 16997 was deleted. The following Werk is no longer relevant.
[//]: # (werk v2)
# NagVis: Updated to 1.9.43
key | value
---------- | ---
date | 2024-08-30T07:45:48+00:00
version | 2.4.0b1
class | fix
edition | cre
component | packages
level | 1
compatible | yes
[//]: # (werk v2)
# SLA alerts levels: show full precision instead of no decimal places
key | value
---------- | ---
date | 2024-08-27T13:08:42+00:00
version | 2.4.0b1
class | fix
edition | cee
component | multisite
level | 1
compatible | yes
SLA alerts levels now show the full precision configured in the SLA rather instead
of no decimal places.
The calculated results of how much SLA is left are still configured within the
view with the `Precision of float values` option.
[//]: # (werk v2)
# Support Diagnostics: Add rotated log files to the dump
key | value
---------- | ---
date | 2024-08-29T12:12:16+00:00
version | 2.4.0b1
class | feature
edition | cre
component | wato
level | 1
compatible | yes
With this werk, it's possible to select rotated logfiles for the dump, for example update.log and update.log.1
In the "Pack only xyz sensitivity files" and "Pack all files" modes, both are are added automatically.
In the "Select individual files from the list" mode, the user can select them separately.
Background: In rare cases, the .log files were empty, because the logging process still wrote into the .log.1 file.
[//]: # (werk v2)
# Support Diagnostics crashes when receiving tar from remote site
key | value
---------- | ---
date | 2024-08-05T11:58:01+00:00
version | 2.4.0b1
class | fix
edition | cre
component | wato
level | 1
compatible | yes
This werk fixes the behavior that creating the support diagnostics crashed when receiving the tar file(s)
from a remote site.
[//]: # (werk v2)
# Jira: Add option to include graphs
key | value
---------- | ---
date | 2024-08-12T08:15:58+00:00
version | 2.4.0b1
class | feature
edition | cee
component | notifications
level | 1
compatible | yes
You can now use the new option "Attach graphs" to include graphs on newly
created issues. The graphs will not be updated afterwards.
If the option is unchecked, no graphs will be attached to the issue.
[//]: # (werk v2)
# Opsgenie: Update description and message
key | value
---------- | ---
date | 2024-08-26T13:13:19+00:00
version | 2.4.0b1
class | feature
edition | cre
component | notifications
level | 1
compatible | yes
The alerts description and message will now be updated.
This requires configuring the integration team name in the plugin.
[//]: # (werk v2)
# Opsgenie: Support other notification types
key | value
---------- | ---
date | 2024-08-26T12:29:57+00:00
version | 2.4.0b1
class | feature
edition | cre
component | notifications
level | 1
compatible | no
Previously, only PROBLEM, RECOVERY and ACKNOWLEDGEMENT notifications were
supported by the Opsgenie plugin. Now the other types are also supported.
Flapping and Downtimes will add or remove tags from the alerts. Alert handler
executions will only add notes.
Due to how alerts are looked up in Opsgenie, the plugin will not be able to
update the alert if it is already closed. This means alert handler executions
that run after the recovery will not be able to add notes to the alert.
In order to enable these changes, the integration team name must be configured
in the plugin.