Title: Decode semi-colon from monitoring history
Class: fix
Compatible: compat
Component: multisite
Date: 1730713541
Edition: cre
Level: 1
Version: 2.2.0p36
The plugin output and comments are saved in a Nagios-compatible format
(semi-colon-separated). Therefore, it is necessary to escape semi-colons
to <code>%3B</code> when writing out history.
In the GUI, where plugin output or comments from the monitoring history
are displayed, we can translate <code>%3B</code> back to a semi-colon using a
simple replace.
Title: oracle_performance: character string buffer too small
Class: fix
Compatible: compat
Component: checks
Date: 1730295667
Edition: cre
Level: 1
Version: 2.2.0p36
In the past it was possible to see <code>PL/SQL: numeric or value error: character
string buffer too small</code> if a PDB name was longer than 11 characters. No memory
performance was available in this case.
This limit was now lifted, it's now possible to use the full length of 128
characters for PDB names. This is the limit for PDB names defined by oracle.
[//]: # (werk v2)
# mk_oracle: iostats performance could not be configured via bakery
key | value
---------- | ---
date | 2024-10-30T19:55:25+00:00
version | 2.3.0p21
class | fix
edition | cee
component | agents
level | 1
compatible | yes
The not configured agent executed the iostat part of the performance section, but
once configured via bakery it was not possible to select this section.
Now it is possible to select it. The option is called "Performance: IO stats"
Please be aware that not many users will benefit from this but have more
load on the system, only. For that reason the option is deactivated by default
in bakery.
[//]: # (werk v2)
# Decode semi-colon from monitoring history
key | value
---------- | ---
date | 2024-11-04T09:45:41+00:00
version | 2.3.0p21
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
The plugin output and comments are saved in a Nagios-compatible format
(semi-colon-separated). Therefore, it is necessary to escape semi-colons
to `%3B` when writing out history.
In the GUI, where plugin output or comments from the monitoring history
are displayed, we can translate `%3B` back to a semi-colon using a
simple replace.
[//]: # (werk v2)
# oracle_performance: character string buffer too small
key | value
---------- | ---
date | 2024-10-30T13:41:07+00:00
version | 2.3.0p21
class | fix
edition | cre
component | checks
level | 1
compatible | yes
In the past it was possible to see `PL/SQL: numeric or value error: character
string buffer too small` if a PDB name was longer than 11 characters. No memory
performance was available in this case.
This limit was now lifted, it's now possible to use the full length of 128
characters for PDB names. This is the limit for PDB names defined by oracle.
[//]: # (werk v2)
# Decode semi-colon from monitoring history
key | value
---------- | ---
date | 2024-11-04T09:45:41+00:00
version | 2.4.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
The plugin output and comments are saved in a Nagios-compatible format
(semi-colon-separated). Therefore, it is necessary to escape semi-colons
to `%3B` when writing out history.
In the GUI, where plugin output or comments from the monitoring history
are displayed, we can translate `%3B` back to a semi-colon using a
simple replace.
[//]: # (werk v2)
# mk_oracle: iostats performance could not be configured via bakery
key | value
---------- | ---
date | 2024-10-30T19:55:25+00:00
version | 2.4.0b1
class | fix
edition | cee
component | agents
level | 1
compatible | yes
The not configured agent executed the iostat part of the performance section, but
once configured via bakery it was not possible to select this section.
Now it is possible to select it. The option is called "Performance: IO stats"
Please be aware that not many users will benefit from this but have more
load on the system, only. For that reason the option is deactivated by default
in bakery.
[//]: # (werk v2)
# Dashboards and graph collections: Fix "There is no graph template with the id 'commit_charge'"
key | value
---------- | ---
date | 2024-10-31T08:08:54+00:00
version | 2.3.0p20
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
The error message mentioned above was raised by certain combined graphs in dashboards and graph
collections. Furthermore, this werk also fixes certain empty template graphs in dashboards and
graph collections.