-
Notifications
You must be signed in to change notification settings - Fork 511
[m365_defender] Add Benchmark and Policy Test #15864
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
base: main
Are you sure you want to change the base?
[m365_defender] Add Benchmark and Policy Test #15864
Conversation
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
| - name: status | ||
| cardinality: 100000 | ||
| - name: severity | ||
| cardinality: 100000 |
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.
Try to get these fields close to real-value because cardinality impacts ES heap metrics.
Here, I think both status and severity cannot have such high cardinality I'm assuming?
| - name: status | ||
| cardinality: 100000 | ||
| - name: severity | ||
| cardinality: 100000 |
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.
same here.
Get the severity and status field closer to the real values.
…m365_defender-add-benchmark
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
History
|
Proposed commit message
Checklist
changelog.ymlfile.How to test this PR locally
Related Issue