ID: 15969
Title: cisco_temperature: Correct warning threshold for environment temperature
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
Currently only the threshold specified by OID 1.3.6.1.4.1.9.9.13.1.3.1.4 (ciscoEnvMonTemperatureThreshold) is considered when checking the temperature of a Cisco switch. As only one threshold is given here, it is used as both WARN and CRIT threshold, causing confusion when the device itself reports a warning state based on a warning threshold not given via this OID.
Now the upper thresholds specified in OID 1.3.6.1.4.1.9.9.91.1.2.1.1 (entSensorThresholdTable) will be used as WARN and CRIT thresholds if an entry for the relevant switch can be found.
For this, the threshold relation and severity will be used to determine if the threshold can be applied in Checkmk, otherwise the threshold will be ignored.
If no thresholds from the entSensorThresholdTable apply, the ciscoEnvMonTemperatureThreshold is used as a fallback.
ID: 15903
Title: cisco_temperature, cisco_temperature_dom: Improved check state and summary if sensor status not ok
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
The cisco_temperature and cisco_temperature_dom checks currently only consider sensors with the state "ok". If a sensor becomes "unavailable" or "non-operational", the check becomes "UNKNOWN" with the summary "Item not found in monitoring data".
With this werk, the summary will now report the status of the sensor instead.
For the "unavailable" sensor status, the check state will still change to "UNKNOWN", for "non-operational" status it will be CRIT.
The discovery is not affected by this and will still only discover "ok" sensors.
ID: 15906
Title: apc_symmetra: Improve wording in ruleset
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
The rule 'Levels of battery parameters after calibration' was actually referring to the time after diagnostics and not calibration.
This has now been corrected and it's clearer what the rule refers to.
ID: 15927
Title: Fix copy of random secret to clipboard
Component: Setup
Level: 1
Class: Bug fix
Version: 2.3.0b1
In some environments, the button "Create random secret and copy secret to
clipboard" of the option "Automation secret for machine accounts" on the users
page did not copy the secret to the clipboard.
We now use a fallback mechanism if the standard fails. If even the fallback
fails you will see a dialog were you can copy the secret manually.
ID: 15078
Title: Merge the postgres_version check into postgres_instances
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.3.0b1
So far, the check plugin postgres_version (services "PostgreSQL Version ...") reported versions of PostgreSQL instances. With this werk, we remove this plugin and instead report the version information in the plugin postgres_instances (services "PostgreSQL Instance ..."). This makes the monitoring of PostgreSQL more consistent with the monitoring of other databases such as Oracle.
Users should execute a service re-discovery on affected hosts to remove already discovered PostgreSQL version services.
ID: 15956
Title: Agent bakery API now available in Checkmk Raw Edition (CRE)
Component: agents
Level: 1
Class: New feature
Version: 2.3.0b1
This werk only concerns developers of custom agent bakery plugins.
The agent bakery API, which allows for registering custom bakery plugins, is now available in the
CRE. This facilitates custom plugin development, since bakery plugins can now be developed in the
context of our GitHub repository with full IDE support. The new import path for the bakery API
reads:
C+:
from cmk.base.plugins.bakery.bakery_api.v1 import register, Plugin, ...
C-:
Note that the old import path is still valid and will continue working. Furthermore, the path in the
hierarchy of the <i>local</i> folder for custom bakery plugins remains unchanged. Hence, MKPs do not
need to be adjusted.
Finally, note that this does of course not mean that the actual bakery functionality is available in
the CRE. Registering a bakery plugin in the CRE will have no effect.
ID: 16019
Title: Update PHP version in SLES15P4 from 7 to 8
Component: RPM Packaging
Level: 2
Class: Bug fix
Version: 2.3.0b1
SLES15P4 ships by default with PHP8, this werk updates the PHP version required and shipped with Checkmk to PHP8
ID: 15566
Title: Exclude sections with mk_oracle.ps1
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0p31
mk_oracle.ps1 provides a configuration to exclude sections for <tt>SID</tt>.
This was only working if you prepend the section name with <tt>sql_</tt>, like e.g.:
C+:
$EXCLUDE_XE="sql_performance"
C-:
If you were using the agent bakery to generate the configuration, the exclude mechansim was not working as it didn't generate the prefix.
It is now not necessary anymore to add this prefix (however with prefix it is stil, like e.g.l working).
In order to apply this fix, the agent plugin <tt>mk_oracle.ps1</tt> must be re-deployed onto your monitored host.