-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[SECURITY SOLUTION] exclude cloud alias index from our query #81551
[SECURITY SOLUTION] exclude cloud alias index from our query #81551
Conversation
Thanks @XavierM
Yes, I like that option. This way, if a user wants to collect their cloud logs, they can replace the |
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.
I like your suggestion of only adding this exclusion when logs-*
is present. We should document this behavior.
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.
💪
💚 Build SucceededMetrics [docs]async chunks size
History
To update your PR or re-run it, just comment with: |
…#81551) * exclude cloud alias index * only exclude cloud alias when logs-* is there
…#81551) * exclude cloud alias index * only exclude cloud alias when logs-* is there
Summary
If a user enabled the new cloud logging functionality, they will end up with a plethora of “hosts” from the logs event even if the user only has 1 endpoint enrolled.
To remediate this problem, we exclude all the elastic cloud logs from all our query inside of the security solution by using this index alias
-*elastic-cloud-logs-*
@MikePaquette if we want we can be a little bit fancier and just excluded
-*elastic-cloud-logs-*
when we have the aliaslogs-*
who has been selected.Checklist