Fail CI when making changes to alerts-as-data ECS mappings that cause migration failures #170339
Labels
Feature:Alerting
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Comments
mikecote
added
Feature:Alerting
Team:ResponseOps
|
Pinging @elastic/response-ops (Team:ResponseOps) |
github-project-automation
bot
moved this to Awaiting Triage
in AppEx: ResponseOps - Execution & Connectors
mikecote
moved this from Awaiting Triage
to Todo
in AppEx: ResponseOps - Execution & Connectors
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a long term solution to #168959, we should detect these migration issues with CI. We current don't have any indicators / quality gates to let us know the latest alerts-as-data mappings will cause migration issues.
When Kibana is upgraded, the alerts-as-data component and index template get updated to the latest mappings and the system goes through the existing alerts-as-data indices to update their mappings. If there is a conflict on a specific field, the operation fails and we may be in a situation where the current write index is not up to date. In the meantime, it's on the manual review process to test upgrading the indices to ensure there isn't a mapping conflict but it would be nice to automate this.
The text was updated successfully, but these errors were encountered: