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.

Sign up for GitHub

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

Jump to bottom

[Response Ops][Alerting] Research generating context and state variables from alerts as data documents #145107

Open
ymao1 opened this issue Nov 14, 2022 · 2 comments
Open

[Response Ops][Alerting] Research generating context and state variables from alerts as data documents #145107

ymao1 opened this issue Nov 14, 2022 · 2 comments
Labels
blocked Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@ymao1
Copy link
Contributor

ymao1 commented Nov 14, 2022

As part of the new Alerts API, we should investigate whether we can generate context and state variables from the information stored inside the alerts as data documents to maintain backwards compatibility for all rule types. Currently, rule type executors explicitly set context and state variables when creating an alert. With the new API, they will be setting fields within the alert documents. We should provide a way for rule types to specify a converter function that takes an alert document with the generic FAAD schema and returns context and state variables. This way we can move closer to deprecating the AlertFactory.
@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 14, 2022
@ymao1 ymao1 mentioned this issue Nov 14, 2022
Open
@ymao1 ymao1 added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework labels Nov 14, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 14, 2022
@ymao1
Copy link
Contributor Author

ymao1 commented Nov 14, 2022

Blocked by #145103

@ymao1 ymao1 added the blocked label Nov 14, 2022
@ymao1 ymao1 moved this from Awaiting Triage to Blocked / On hold in AppEx: ResponseOps - Execution & Connectors Nov 14, 2022
@ymao1 ymao1 mentioned this issue Jan 11, 2023
Closed
@mikecote mikecote moved this from Blocked / On hold to On Hold in AppEx: ResponseOps - Execution & Connectors Dec 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
AppEx: ResponseOps - Execution & Connectors
Status: On Hold
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ymao1 @elasticmachine