-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Alerts] Use unmapped_type: keyword for unmapped fields in alerts query #198624
base: main
Are you sure you want to change the base?
[Alerts] Use unmapped_type: keyword for unmapped fields in alerts query #198624
Conversation
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations) |
💔 Build Failed
Failed CI Steps
Test Failures
Metrics [docs]Async chunks
History |
I can see the following from some of the failed tests:
Guessing the new |
Ya that sounds about right, I will dig a little deeper on this, probably should have opened this as a draft pr first. Mostly just wanted to show @kapral18 that this is "all" (outside of validation/any tightly coupled to the es request body tests) we have to do to fix this in most cases, and it's a pretty common source of SDHs. |
For reference, and to decrease the # of searches I need to make for this, the |
Summary
Currently if a user tries to sort the alerts table by an umapped field, for instance data_stream.dataset, the table will show 0 results, with no easy way to remove this sort. Adds unmapped_type: keyword to the alerts query to help mitigate this, but there should be a ux way to clear filters/sort as well. Related: #170167 and #171104
Checklist