[gcp] Remove emtpy values, names with only dots, and invalid client IPs. #2747
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
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
P1llus
reviewed
Feb 28, 2022
packages/gcp/data_stream/audit/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
packages/gcp/data_stream/audit/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
P1llus
approved these changes
Mar 1, 2022
eyalkraft
pushed a commit
to build-security/integrations
that referenced
this pull request
Mar 30, 2022
…Ps. (elastic#2747) * Remove emtpy values, names with only dots, and invalid client IPs. * Keep raw client ip, add description, and override orchestrator fields * Re generate README.md * Remove newlines from field descriptions
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.
What does this PR do?
Some gcp events contain keys that are formed only by dots, and also can contain invalid ip fields. This change cleans up both.
Checklist
changelog.ymlfile.