-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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] Cleanup after ExecLog integration #107695
Conversation
240231e
to
49667f7
Compare
f5d1521
to
57d7cfd
Compare
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
d69bf03
to
28bc8bb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me overall 👍
What I did:
- reviewed the code changes and compared them to the deleted implementation of rule status service
- tested the PR locally, didn't notice any issues
Thank you for this cleanup. I left a few small comments.
...lution/server/lib/detection_engine/rule_execution_log/__mocks__/rule_execution_log_client.ts
Show resolved
Hide resolved
...ecurity_solution/server/lib/detection_engine/rule_types/create_security_rule_type_factory.ts
Show resolved
Hide resolved
...ck/plugins/security_solution/server/lib/detection_engine/signals/rule_status_service.test.ts
Show resolved
Hide resolved
...erver/lib/detection_engine/rule_execution_log/saved_objects_adapter/saved_objects_adapter.ts
Outdated
Show resolved
Hide resolved
...erver/lib/detection_engine/rule_execution_log/saved_objects_adapter/saved_objects_adapter.ts
Show resolved
Hide resolved
28bc8bb
to
2c1be08
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thank you for the changes. Let's merge this guy 🙂 🚀
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @xcrzx |
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
Co-authored-by: Dmitry Shevchenko <[email protected]>
Related to: #106461, #106466
Summary
It's a follow-up PR to clean up leftovers after ExecutionLog integration.
Notable changes:
Removed
RuleStatusService
RuleStatusService
contained mainly logic related to Saved Objects implementation which was moved torule_execution_log/saved_objects_adapter
. All usages ofRuleStatusService
were replaced withRuleExecutionLogClient
.Before:
After:
RuleExecutionLogClient
interface changescreate()
method was removed in favor of more specificlogStatusChange()
andlogExecutionMetric()
methods.logStatusChange()
method arguments now acceptmetrics
object to simulate behavior of the oldRuleStatusService
. This is a temporary solution. In the future we should write all execution metrics separately usinglogExecutionMetric()
.RuleStatusSavedObjectsClient
moved torule_execution_log/saved_objects_adapter
RuleStatusSavedObjectsClient
was moved torule_execution_log/saved_objects_adapter
directory. It is considered internal implementation of theRuleExecutionLog
from now on and should not be used directly.Checklist