Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Cherry-pick #10135 to 6.6: Elasticsearch/audit fileset should be more lenient in parsing node name #10465

Merged
merged 3 commits into from
Feb 1, 2019
Merged

Cherry-pick #10135 to 6.6: Elasticsearch/audit fileset should be more lenient in parsing node name #10465

merged 3 commits into from
Feb 1, 2019

Commits on Jan 31, 2019

  1. Elasticsearch/audit fileset should be more lenient in parsing node na… 

    …me (#10135)

Resolves #10035.

This PR:

* Uses `DATA` instead of `WORD` in the grok pattern for parsing out `elasticsearch.node.name`,
* Breaks out the grok pattern into pattern definitions to increase readability
* Removes a redundant `?` after a `*` in the grok pattern (between `elasticsearch.audit.action` and `elasticsearch.audit.uri`), and
* Properly reindents the pipeline JSON (so you might want to view the diff with `?w=1` appended to the URL)

(cherry picked from commit 93851c2)
    @ycombinator
    ycombinator committed Jan 31, 2019
    Configuration menu
    Copy the full SHA
    dc17df2 View commit details
    Browse the repository at this point in the history

  2. Regenerating golden file

    @ycombinator
    ycombinator committed Jan 31, 2019
    Configuration menu
    Copy the full SHA
    4a40a1f View commit details
    Browse the repository at this point in the history

  3. Remove CHANGELOG entries not from this PR

    @ycombinator
    ycombinator committed Jan 31, 2019
    Configuration menu
    Copy the full SHA
    745beb7 View commit details
    Browse the repository at this point in the history