Skip to content

[8.11] [Response Ops][Alerting] Remove echoed field value from bulk error responses when indexing alerts (#172020)#172085

Merged
kibanamachine merged 1 commit intoelastic:8.11from
kibanamachine:backport/8.11/pr-172020
Nov 28, 2023
Merged

[8.11] [Response Ops][Alerting] Remove echoed field value from bulk error responses when indexing alerts (#172020)#172085
kibanamachine merged 1 commit intoelastic:8.11from
kibanamachine:backport/8.11/pr-172020

Conversation

@kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 8.11:

Questions ?

Please refer to the Backport tool documentation

…sponses when indexing alerts (elastic#172020)

## Summary

When alerts are bulk indexed in the rule registry and the alerts client,
indexing errors may be returned where the entire field value that failed
to be indexed is echoed in the reason. This can cause unnecessarily
verbose logging so we want to sanitize the field value.

(cherry picked from commit d9ebfd9)
@kibana-ci
Copy link

💚 Build Succeeded

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id before after diff
alerting 754 756 +2
Unknown metric groups

API count

id before after diff
alerting 785 787 +2

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @ymao1

@kibanamachine kibanamachine merged commit 35393bc into elastic:8.11 Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants