Title: re-use of context in multiple threads in activate changes
Class: fix
Compatible: compat
Component: core
Date: 1697705777
Edition: cre
Knowledge: doc
Level: 1
Version: 2.2.0p13
When running "activate changes", a "context" object is created and
passed to multiple threads. The concurrent use of this context is
not supported and can lead to crashes.
As a fix, now every thread receives their own copy of the context
leading to complete isolation of the threads.
No further action is required to activate the fix.
Title: Restrict the group name pattern to disallow incompatible names
Class: fix
Compatible: compat
Component: wato
Date: 1697196846
Edition: cre
Level: 1
Version: 2.3.0b1
Before this werk it was possible to create groups with names that could not be accessed from the REST API. This werk restricts the group name pattern and prevents the creation of incompatible groups names like '.' and '..' from both WATO and the REST API.
Title: This Werk fixes misbehaved metrics after an upgrade
Class: fix
Compatible: compat
Component: checks
Date: 1697611822
Edition: cre
Level: 1
Version: 2.3.0b1
After an upgrade various plugins metrics would misbehave, until eventually settling again.
More specificly: All averaged metrics would forget the previously recorded values.
As a result, the "averaged" metric follows the original one very closely.
After a few values are recorded the desired smoothing effect of the averaging will start to show.
The time it takes for the metric to stabilise depends on the configured or implemented weights (<i>"Backlog in minutes"</i>).
Title: Correct the response schemes in audit log endpoints
Class: fix
Compatible: compat
Component: rest-api
Date: 1697026334
Edition: cre
Knowledge: doc
Level: 1
Version: 2.3.0b1
This werk removes the 'link' attributes from the response schema as these endpoints do not provide such information.
Werk 16136 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: api-docs: include explanation of the special character * for the If-Match header
Class: fix
Compatible: compat
Component: rest-api
Date: 1695723736
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p11
Most PUT requests to the REST API require an If-Match header containing
an ETag. With this Werk we make it possible to provide "*" instead of an
ETag, like this: "If-Match": "*"
This Werk also adds a short explanation to the REST API documentation.
See the section "Updating values" for more information.
------------------------------------<diff>-------------------------------------------
Title: api-docs: include explanation of the special character * for the If-Match header
Class: fix
Compatible: compat
Component: rest-api
Date: 1695723736
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p11
- We recently made changes to make it possible to provide the following header
- in rest-api requests
- "If-Match": "*"
+ Most PUT requests to the REST API require an If-Match header containing
+ an ETag. With this Werk we make it possible to provide "*" instead of an
+ ETag, like this: "If-Match": "*"
- instead of providing a resource's ETag.
+ This Werk also adds a short explanation to the REST API documentation.
+ See the section "Updating values" for more information.
- This werk adds a short explanation to the api-docs so that our users know
- that this is possible.
-
-
-
Werk 16136 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: api-docs: include explanation of the special character * for the If-Match header
Class: fix
Compatible: compat
Component: rest-api
Date: 1695723736
Edition: cre
Knowledge: doc
Level: 1
Version: 2.3.0b1
Most PUT requests to the REST API require an If-Match header containing
an ETag. With this Werk we make it possible to provide "*" instead of an
ETag, like this: "If-Match": "*"
This Werk also adds a short explanation to the REST API documentation.
See the section "Updating values" for more information.
------------------------------------<diff>-------------------------------------------
Title: api-docs: include explanation of the special character * for the If-Match header
Class: fix
Compatible: compat
Component: rest-api
Date: 1695723736
Edition: cre
Knowledge: doc
Level: 1
Version: 2.3.0b1
- We recently made changes to make it possible to provide the following header
- in rest-api requests
- "If-Match": "*"
+ Most PUT requests to the REST API require an If-Match header containing
+ an ETag. With this Werk we make it possible to provide "*" instead of an
+ ETag, like this: "If-Match": "*"
+ This Werk also adds a short explanation to the REST API documentation.
+ See the section "Updating values" for more information.
- instead of providing a resource's ETag.
-
- This werk adds a short explanation to the api-docs so that our users know
- that this is possible.
-
-
Title: Fix permission "Move to monitored services" in service discovery
Class: fix
Compatible: compat
Component: wato
Date: 1697785479
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.1.0p36
If users with permission "Move to monitored services" tried to move undecided
services to monitored services, it was stated that the user needs the
permission "Move to undecided services", what was wrong.
Title: check_mail and check_mail_loop: Enable EWS and OAuth2
Class: feature
Compatible: compat
Component: checks
Date: 1697097112
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.1.0p36
In response to the <a href="https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-o…">deprecation of basic authentication</a> for Microsoft mail services, EWS and OAuth2 are enabled for the active checks check_mail ("Check Email") and check_mail_loop ("Check Email Delivery"), as was done for check_mailboxes ("Check IMAP/EWS Mailboxes") already.
Users can now configure their respective check rules to fetch (and in case of check_mail_loop send) mails via EWS and OAuth2.
Note that some command line options for the underlying active check commands have changed. So for calling these checks directly from the command line, users will need to look into the command usage help to find the updated options. Check configurations set up in the UI, however, are migrated to the new structure and thus need no further action.