[Security Solution][Entity Analytics][RiskScoring] Adding changes for backporting #247060 to 9.1#247332
Closed
abhishekbhatia1710 wants to merge 4 commits intoelastic:9.1from
Closed
Conversation
Contributor
|
Pinging @elastic/security-entity-analytics (Team:Entity Analytics) |
Contributor
|
@elasticmachine merge upstream |
Contributor
|
Closing this PR, as I misunderstood the issue with this one in our standup call. ES|QL based risk scoring wasn't introduced until 9.2, so no need to backport this change to 9.1. |
Contributor
⏳ Build in-progress, with failures
Failed CI StepsTest Failures
History
|
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
Backport changes of #247060 to
9.1Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:*label is applied per the guidelinesbackport:*labels.