[DOCS] Troubleshooting alerting upgrade issues (#139970)

This commit is contained in:
Lisa Cawley 2022-09-07 09:36:55 -07:00 committed by GitHub
parent db7bf5f0d8
commit 059e18c151
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -266,3 +266,23 @@ This error happens when the `xpack.encryptedSavedObjects.encryptionKey` value us
| Generate a new API key for the rule by disabling then enabling the rule.
|===
[float]
[[known-issue-upgrade-rule]]
==== Rules stop running after upgrade
*Problem*:
Alerting rules that were created or edited in 8.2 stop running after you upgrade
to later releases. The following error occurs:
[source,text]
----
<rule-type>:<UUID>: execution failed - security_exception: [security_exception] Reason: missing authentication credentials for REST request [/_security/user/_has_privileges], caused by: ""
----
*Solution*:
Upgrade to 8.3.2 or later releases, then go to *{stack-manage-app} > {rules-ui}* and multi-select the failed rules. Choose
**Manage rules > Update API Keys** to generate new API keys. For more details
about API key authorization, refer to <<alerting-authorization>>.