Cherry-pick #10135 to 6.6: Elasticsearch/audit fileset should be more lenient in parsing node name #10465
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.
Cherry-pick of PR #10135 to 6.6 branch. Original message:
Resolves #10035.
This PR:
DATA
instead ofWORD
in the grok pattern for parsing outelasticsearch.node.name
,?
after a*
in the grok pattern (betweenelasticsearch.audit.action
andelasticsearch.audit.uri
), and?w=1
appended to the URL)