github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 09:48:58 -04:00
Code Issues Projects Releases Packages Wiki Activity

[8.3][DOCS] Adds known issue to 8.3.0. (#139471)

Browse source
This commit is contained in:
István Zoltán Szabó 2022-08-25 14:04:45 +02:00 • committed by GitHub
parent 7e8898e220
commit 34bad2239b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 46 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

50
docs/CHANGELOG.asciidoc
View file

@ -251,15 +251,18 @@ Review the following information about the {kib} 8.3.0 release.
[[known-issues-8.3.0]]
=== Known issues
[discrete]
==== Alerting rules stop running on upgrade
Alerting users who are running 8.2 should not upgrade to either 8.3.0 or 8.3.1.
Both 8.3.0 and 8.3.1 have a bug where alerting rules that were created or edited
in 8.2 will stop running on upgrade. If you have upgraded to 8.3.0 or 8.3.1 and
your alerting rules have stopped running with an error similar to the following
example, you will need to go to *{stack-manage-app} > {rules-ui}*, multi-select
the failed rules, click on **Manage rules > Disable** and then click on **Manage
rules > Enable**. Disabling and re-enabling the rule will generate a new API key
using the credentials of the user performing these actions and reset the rule
state. For more details about API key authorization, refer to
the failed rules, click on **Manage rules > Disable** and then click on
**Manage rules > Enable**. Disabling and re-enabling the rule will generate a
new API key using the credentials of the user performing these actions and reset
the rule state. For more details about API key authorization, refer to
<<alerting-authorization>>.
Example error message::
@ -269,6 +272,45 @@ Example error message::
<rule-type>:<UUID>: execution failed - security_exception: [security_exception] Reason: missing authentication credentials for REST request [/_security/user/_has_privileges], caused by: ""
----
[discrete]
==== Snoozed alerting rules need to be cancelled before upgrade
If you have alerting rules that have been snoozed, do not upgrade {kib} from
8.3.3 to 8.4.0.
To determine if you have snoozed alerting rules, open the main menu, then click
**Stack Management** -> **Rules and Connectors**.
Filter the rule list by selecting **View** -> **Snoozed**.
For each space, cancel the snooze for all affected rules before you upgrade.
To identify snoozed rules in all Spaces using **Dev Tools**, run the following
query:
[source,console]
----
GET /.kibana/_search
{
"query": {
"exists": {
"field": "alert.isSnoozedUntil"
}
}
}
----
When you upgrade {kib} from 8.3.3 to 8.4.0, and you have alerting rules
configured to snooze notifications, you will receive the following error
message:
[source,text]
----
FATAL Error: Unable to complete saved object migrations for the [.kibana] index.
----
Before you retry the upgrade, restore your previous version, then cancel any
alerting rules with snooze notifications.
[float]
[[breaking-changes-8.3.0]]
=== Breaking change