Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability for alert / action types to define migrations #50216

Open
mikecote opened this issue Nov 11, 2019 · 6 comments
Open

Ability for alert / action types to define migrations #50216

mikecote opened this issue Nov 11, 2019 · 6 comments
Labels
DX Issues related to Developer Experience estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/Framework Issues related to the Actions Framework Feature:Actions Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Feature:Alerting migration-resilience Issues related to migration resilience in terms of scale, performance & backwards compatibility NeededFor:Detections and Resp NeededFor:logs-metrics-ui Project:MoreRuleTypes Alerting team project for providing more ways to construct rules. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

mikecote commented Nov 11, 2019

In scenario they changed the parameters for their alert / action type.
In the scenario we added name to alert.

This will be needed once we support mappings for config, params, etc

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-stack-services (Team:Stack Services)

@mikecote
Copy link
Contributor Author

Some additional comments in issue #66608

@mikecote
Copy link
Contributor Author

mikecote commented Dec 4, 2020

Linking with #84907 as it could help us here.

@spong
Copy link
Member

spong commented Dec 7, 2020

+1 here from the Security Detections side. It would be beneficial for us to be able to leverage dedicated SO migrations for Detection Rules (and not having to embed the migration within Alerting). A recent example here is in needing to find all Detection Rules that reference a set of Exception Lists, whose reference is currently being stored in the Rule's AlertParams and cannot be searched. We don't currently have a back reference on our Exception Lists, so one solution would be to move the Rule's Exception List reference from AlertParams to internal tags within an SO migration (or leverage the existing SO references array).

@mikecote
Copy link
Contributor Author

mikecote commented Feb 4, 2021

Moving from 7.x - Candidates to 8.x - Candidates (Backlog) after the latest 7.x planning session.

@stacey-gammon
Copy link
Contributor

stacey-gammon commented Jun 17, 2021

@joshdover @ppisljar - This looks like another use case for Persistable State. This is an interesting one though because it appears that the registrar can define mappings on the saved object. I was hoping we could get away with just leveraging "migrateToLatest" functionality rather than the SO-required object mapping (of version to migrate function), but because of this use case, we may need to continue to support both.

@gmmorris gmmorris added NeededFor:logs-metrics-ui NeededFor:Detections and Resp Project:MoreRuleTypes Alerting team project for providing more ways to construct rules. Feature:Actions/Framework Issues related to the Actions Framework Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Feature:Actions labels Jun 30, 2021
@gmmorris gmmorris added the loe:large Large Level of Effort label Jul 14, 2021
@gmmorris gmmorris added loe:needs-research This issue requires some research before it can be worked on or estimated and removed loe:large Large Level of Effort labels Jul 14, 2021
@gmmorris gmmorris added DX Issues related to Developer Experience migration-resilience Issues related to migration resilience in terms of scale, performance & backwards compatibility estimate:needs-research Estimated as too large and requires research to break down into workable issues labels Aug 13, 2021
@gmmorris gmmorris removed the loe:needs-research This issue requires some research before it can be worked on or estimated label Sep 2, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DX Issues related to Developer Experience estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/Framework Issues related to the Actions Framework Feature:Actions Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Feature:Alerting migration-resilience Issues related to migration resilience in terms of scale, performance & backwards compatibility NeededFor:Detections and Resp NeededFor:logs-metrics-ui Project:MoreRuleTypes Alerting team project for providing more ways to construct rules. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
Development

No branches or pull requests

7 participants