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

[Security Solution][Detections] Migrate from shadow saved object for managing actions configured to fire at specific intervals #100958

Closed
spong opened this issue May 28, 2021 · 4 comments
Assignees
Labels
Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. technical debt Improvement of the software architecture and operational architecture

Comments

@spong
Copy link
Member

spong commented May 28, 2021

Currently the Detection Engine uses a few separate SO's for managing additional state, sometimes as a stopgap while other solutions were under development. Details on all SO's managed by Detections are detailed in this comment here: #60053 (comment).

Actions/Notifications SO's:

For managing Rule Actions that run at configured intervals (instead of at rule execution) the initial implementation included an additional shadow SO -- this issue is for investigating if it's possible to remove this additional shadow SO in favor of leveraging the functionality from the underlying alerting framework.

Custom Action Interval from Core Alerting UI:

@spong spong added technical debt Improvement of the software architecture and operational architecture Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. 7.15 candidate labels May 28, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@FrankHassanabad
Copy link
Contributor

Other two discuss tickets:
#112327
#112209

@yctercero
Copy link
Contributor

Addressed in 7.16 - related work found here.

Closing out for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. technical debt Improvement of the software architecture and operational architecture
Projects
None yet
Development

No branches or pull requests

4 participants