maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add "Unable to decrypt attribute apiKey" to the alerting troubleshooting docs (#101315)

Browse source 
* Initial commit

* PR feedback

* PR feedback pt 2

* PR feedback pt 3
This commit is contained in:
Mike Côté 2021-06-22 12:30:40 -04:00 committed by GitHub
parent 19d2d17158
commit 5ffe26cbf3
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 26 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
docs/user/alerting/alerting-troubleshooting.asciidoc
View file

@ -12,6 +12,32 @@ If your problem isn’t described here, please review open issues in the followi
Have a question? Contact us in the https://discuss.elastic.co/[discuss forum].
[float]
[[rule-cannot-decrypt-api-key]]
=== Rule cannot decrypt apiKey
*Problem*:
The rule fails to execute and has an `Unable to decrypt attribute "apiKey"` error.
*Solution*:
This error happens when the `xpack.encryptedSavedObjects.encryptionKey` value used to create the rule does not match the value used during rule execution. Depending on the scenario, there are different ways to solve this problem:
[cols="2*<"]
|===
| If the value in `xpack.encryptedSavedObjects.encryptionKey` was manually changed, and the previous encryption key is still known.
| Ensure any previous encryption key is included in the keys used for <<xpack-encryptedSavedObjects-keyRotation-decryptionOnlyKeys, decryption only>>.
| If another {kib} instance with a different encryption key connects to the cluster.
| The other {kib} instance might be trying to run the rule using a different encryption key than what the rule was created with. Ensure the encryption keys among all the {kib} instances are the same, and setting <<xpack-encryptedSavedObjects-keyRotation-decryptionOnlyKeys, decryption only keys>> for previously used encryption keys.
| If other scenarios don't apply.
| Generate a new API key for the rule by disabling then enabling the rule.
|===
[float]
[[rules-small-check-interval-run-late]]
=== Rules with small check intervals run late
@ -29,7 +55,6 @@ Either tweak the <<task-manager-settings,{kib} Task Manager settings>> or increa
For more details, see <<task-manager-health-scheduled-tasks-small-schedule-interval-run-late>>.
[float]
[[scheduled-rules-run-late]]
=== Rules run late