[Security Solution][Detections] Enable writing rule execution events to Event Log by default #115394
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
banderror
added
auto-backport
|
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
|
Pinging @elastic/security-solution (Team: SecuritySolution) |
spong
approved these changes
Oct 18, 2021
There was a problem hiding this comment.
Checked out, tested locally, and verified Rule Execution Events were being written to the EventLog (and all existing functionality with Rule Monitoring/Details behaved as expected w/ the RuleStatus SO). So happy to finally enable this -- no going back now, thanks @banderror!! 🙂 🚀
|
@elasticmachine merge upstream edit: A little preemptive -- build is going to fail until #115440 is merged. Will re-merge once that makes it in. |
|
@elasticmachine merge upstream |
1 similar comment
|
@elasticmachine merge upstream |
banderror
force-pushed
the
enable-event-log-adapter-by-default
branch
from
ef99110 to
77453f3
Compare
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: cc @banderror |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Oct 19, 2021
…to Event Log by default (elastic#115394) * Enable writing rule execution events to Event Log by default * Update event log provider name according to the RFC * Fix SavedObjectClient find method arguments Co-authored-by: Dmitry Shevchenko <[email protected]>
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
kibanamachine
added a commit
that referenced
this pull request
Oct 19, 2021
…to Event Log by default (#115394) (#115630) * Enable writing rule execution events to Event Log by default * Update event log provider name according to the RFC * Fix SavedObjectClient find method arguments Co-authored-by: Dmitry Shevchenko <[email protected]> Co-authored-by: Georgii Gorbachev <[email protected]> Co-authored-by: Dmitry Shevchenko <[email protected]>
19 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tickets: #106469, #101013
Summary
securitySolution.ruleExecutionaccording to the RFC.Config setting
The default config setting is now:
The behaviour by default is now as follows:
siem-detection-engine-rule-statussaved objectssiem-detection-engine-rule-statussiem-detection-engine-rule-statusfor both the Rule Management page and the Rule Details pageIf we notice any issues with Rule Monitoring in Security before the 7.16.0 release, we will revert the default value to
savedObjects.Checklist