[//]: # (werk v2)
# Fix "Parsing of section rmon_stats failed" for Cisco SNMP devices
key | value
---------- | ---
date | 2024-07-10T07:45:41+00:00
version | 2.3.0p10
class | fix
edition | cre
component | checks
level | 1
compatible | no
For certain Cisco devices, the _Check\_MK Discovery_ service and the service discovery page
displayed the error message mentioned above. To solve this issue, users have to execute the _Remove
all and find new_ action in the actions menu of the service discovery page for affected hosts.
[//]: # (werk v2)
# Ensure background jobs finish properly on stopping sites
key | value
---------- | ---
date | 2024-07-09T14:38:01+00:00
version | 2.4.0b1
class | fix
edition | cre
component | core
level | 2
compatible | yes
Previously running background jobs were not properly cleaned up by `omd stop`.
Those processes were terminated at the end of `omd stop` command which would
clean up the processes in most cases, but lead to failed jobs and leave crash
reports behind.
Secondly a few background jobs depend on Redis. In case Redis is stopped while
the jobs are still running, the jobs would fail and also leave a crash report
behind.
This change aims to solve both issues, by extending what happens during
`omd stop`. The procedure roughly works like this:
1. First the apache process and site cron are stopped to prevent the
start of new background jobs. This is done by the already existing logic.
2. The new init script `background-jobs` gives the jobs some time to finish.
Ideally all jobs are stopped after 20 seconds.
3. The stop command does not have to forcefully kill the jobs anymore in this case.
4. As a last resort `omd stop` will terminate the still running jobs as before.
[//]: # (werk v2)
# Fix "Parsing of section rmon_stats failed" for Cisco SNMP devices
key | value
---------- | ---
date | 2024-07-10T07:45:41+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
For certain Cisco devices, the _Check\_MK Discovery_ service and the service discovery page
displayed the error message mentioned above. To solve this issue, users have to execute the _Remove
all and find new_ action in the actions menu of the service discovery page for affected hosts.
[//]: # (werk v2)
# missing error message for wrong backup key password
key | value
---------- | ---
date | 2024-07-02T12:50:08+00:00
version | 2.4.0b1
class | fix
edition | cre
component | wato
level | 1
compatible | yes
When a wrong password was entered for downloading a backup encryption key or a signature key for signing agents, an empty error message box was displayed.
Now, the error message is displayed correctly.
Title: infoblox_service: Add support for NIOS 9.X
Class: fix
Compatible: incomp
Component: checks
Date: 1718697625
Edition: cre
Level: 1
Version: 2.2.0p31
With newer infoblox NIOS devices the <code>IB-PLATFORMONE-MIB::IBServiceName</code> have
changed. We use these name as service items. Please run a re-discovery on the
affected hosts.
[//]: # (werk v2)
# infoblox_service: Add support for NIOS 9.X
key | value
---------- | ---
compatible | no
version | 2.3.0p10
date | 2024-06-18T08:00:25+00:00
level | 1
class | fix
component | checks
edition | cre
With newer infoblox NIOS devices the <code>IB-PLATFORMONE-MIB::IBServiceName</code> have
changed. We use these name as service items. Please run a re-discovery on the
affected hosts.
Werk 17074 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# msexch_database: Use consistent units (ms/s) in rules & graphs
key | value
---------- | ---
date | 2024-06-18T07:20:14+00:00
version | 2.3.0p7
class | fix
edition | cee
component | checks
level | 1
compatible | yes
The msexch_database reported its values in ms in the summary/ruleset but
displayed the same value as seconds in the graph. With this werk, all
units will be reported consistently.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
- # MS Exchange: Use consistent units (ms/s) in rules & graphs
? ^^^^ ^^
+ # msexch_database: Use consistent units (ms/s) in rules & graphs
? ^^^ ++ ^^^^^
key | value
---------- | ---
date | 2024-06-18T07:20:14+00:00
version | 2.3.0p7
class | fix
edition | cee
component | checks
level | 1
compatible | yes
- Various msexch_* checks reported its values in ms in the summary/ruleset
? ^^^^^^^ ^^^^ ---
+ The msexch_database reported its values in ms in the summary/ruleset but
? ^^^ ^^^^^^^ ++++
- but displayed the same value as seconds in the graph. With this werk,
? ----
+ displayed the same value as seconds in the graph. With this werk, all
? ++++
- all units will be reported consistently.
? ----
+ units will be reported consistently.
[//]: # (werk v2)
# MS Exchange: Use consistent units (ms/s) in rules & graphs
key | value
---------- | ---
compatible | yes
version | 2.3.0p10
date | 2024-07-08T10:10:57+00:00
level | 1
class | fix
component | checks
edition | cre
The checks msexch_isclienttype, msexch_isstore, msexch_rpcclientaccess reported
their values in ms in the summary/ruleset but displayed the same value as
seconds in the graph. With this werk, all MS Exchange checks now report their
values consistently.
[//]: # (werk v2)
# Servicenow: New option for authentication with OAuth token
key | value
---------- | ---
date | 2024-07-09T06:27:58+00:00
version | 2.4.0b1
class | feature
edition | cee
component | notifications
level | 1
compatible | yes
You can now use OAuth token to authenticate against your Servicenow instance.
The token can be entered in the new authentication section within the
notification method configuration if you choose "OAuth token authentication".
For configuration of OAuth within Servicenow, please refer to the Servicenow
documentation.
[//]: # (werk v2)
# Servicenow: Add option to use custom fields
key | value
---------- | ---
date | 2024-07-08T13:34:21+00:00
version | 2.4.0b1
class | feature
edition | cee
component | notifications
level | 1
compatible | yes
You can now use the "Custom fields" option in the parameters of the Servicenow
notification plugin to add custom fields of your incident or case template.
This is useful if you have configured mandatory custom fields within Servicenow
that have to be filled on creation, update oder close of an incident or case.