[Security Solution][Detections] Add alert source to detection rule action context#85488
Merged
marshallmain merged 6 commits intoelastic:masterfrom Dec 15, 2020
Merged
Conversation
Contributor
Author
|
@elasticmachine merge upstream |
Contributor
Author
|
jenkins test this |
Contributor
Author
|
@elasticmachine merge upstream |
madirey
approved these changes
Dec 14, 2020
Contributor
|
Reviewed, pulled, and tested that notifications fire. Looks good! |
marshallmain
added a commit
to marshallmain/kibana
that referenced
this pull request
Dec 15, 2020
…tion context (elastic#85488) * Adds context.alerts as available parameter for detection rule actions Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
gmmorris
added a commit
to ymao1/kibana
that referenced
this pull request
Dec 15, 2020
* master: (66 commits) [Alerting] fixes broken Alerting Example plugin (elastic#85774) [APM] Service overview instances table (elastic#85770) [Security Solution] Unskip timeline creation Cypress test (elastic#85871) properly recognize enterprise licenses (elastic#85849) [SecuritySolution][Detections] Adds SavedObject persistence to Signals Migrations (elastic#85690) [TSVB] Fix functional tests flakiness and unskip them (elastic#85388) [Fleet] Change permissions for Fleet enroll role (elastic#85802) Gauge visualization can no longer be clicked to filter on values since Kibana 7.10.0 (elastic#84768) [Security Solution][Detections] Add alert source to detection rule action context (elastic#85488) [Discover] Don't display hide/show button for histogram when there's no time filter (elastic#85424) skip flaky suite (elastic#78553) License checks for alerts plugin (elastic#85649) skip flaky suite (elastic#84992) skip 'query return results valid for scripted field' elastic#78553 Allow action types to perform their own mustache variable escaping in parameter templates (elastic#83919) [ML] More machine learning links in doc_links_service.ts (elastic#85365) Removed Alerting & Event Log deprecated fields that should not be using (elastic#85652) Closes elastic#79995 by adding new tab in transaction details to show related trace logs. (elastic#85859) Fix outdated jest snapshot [Maps] Surface on prem EMS (elastic#85729) ...
So this pull request going to give the ability to add following for context fields? |
|
@austinsonger Yes, any fields in the document that are present will be able to be used as context for external actions. |
Contributor
💔 Build Failed
Failed CI Steps
Test FailuresJest Integration Tests.src/core/server/ui_settings/integration_tests.uiSettings/routes doc exists get route returns a 200 and includes userValuesStandard OutStack TraceJest Integration Tests.src/core/server/ui_settings/integration_tests.uiSettings/routes doc exists set route returns a 200 and all values including updateStandard OutStack TraceJest Integration Tests.src/core/server/ui_settings/integration_tests.uiSettings/routes doc exists set route returns a 400 if trying to set overridden valueStandard OutStack Traceand 4 more failures, only showing the first 3. Metrics [docs]Async chunks
Distributable file count
Page load bundle
History
To update your PR or re-run it, just comment with: |
This file contains hidden or 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
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.
Summary
This PR adds the source of the detection alert documents to the rule action context so notification actions can access fields within the detection alerts. The source alerts are available as an array through Mustache templating at
{{context.alerts}}, e.g.{{context.alerts.0.process.name}}would get the process.name field of the first alert.Docs update: Alert data is now available in detection rule actions at {{context.alerts}} as an array. This array contains each alert generated since the last time the action executed. Mustache templating can be used to iterate over all alerts in the array and capture information from each one. For example,
{{#context.alerts}}Detection alert for user: {{user.name}}{{/context.alerts}}would create the stringDetection alert for user: <user.name>for every alert in the array. Any alerts that don't haveuser.namewill still generate the string but leave<user.name>blank.Test process:
http://localhost:<some port>with no auth and no http header, ex/kibana/x-pack/plugins/security_solution/public/detections/components/rules/throttle_select_field/index.tsxdown to 5m or less so you don't have to wait an hour for the action to triggersudo nc -l 392on ubuntu listens on port 392.Checklist
Delete any items that are not applicable to this PR.
For maintainers