[SecuritySolution][Threat Hunting] Use correct field ids for ML, ransomware, indicator alerts #125937
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
janmonschke
added
bug
|
Pinging @elastic/security-solution (Team: SecuritySolution) |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @janmonschke |
kqualters-elastic
approved these changes
Feb 22, 2022
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Feb 22, 2022
…omware, indicator alerts (elastic#125937) * fix: use correct field ids for ML, ransomware, threat matching events * copy: remove unused translations Co-authored-by: Kibana Machine <[email protected]> (cherry picked from commit be4caac)
kibanamachine
added a commit
that referenced
this pull request
Feb 22, 2022
…omware, indicator alerts (#125937) (#126131) * fix: use correct field ids for ML, ransomware, threat matching events * copy: remove unused translations Co-authored-by: Kibana Machine <[email protected]> (cherry picked from commit be4caac) Co-authored-by: Jan Monschke <[email protected]>
lucasfcosta
pushed a commit
to lucasfcosta/kibana
that referenced
this pull request
Mar 2, 2022
…omware, indicator alerts (elastic#125937) * fix: use correct field ids for ML, ransomware, threat matching events * copy: remove unused translations Co-authored-by: Kibana Machine <[email protected]>
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
Issues #125480, #125492, #125473 show that some of the field ids in the alert flyout were incorrect.
This PR updates the affected field ids with ids from the real-world scenarios that were provided in the issues above.
Checklist