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.

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

[7.x] Fixing node name to use DATA grok pattern (#14547) #14582

Merged
merged 3 commits into from
Nov 19, 2019

Conversation

ycombinator
Copy link
Contributor

Backports the following commits to 7.x:

* Fixing node name to use `DATA` grok pattern

Previously, the node name field was being parsed using the `WORD` grok patterns, which does not allow for characters such as `-` in the node name. Such characters are acceptable in Elasticsearch node names, so this PR fixes the grok expression to try and parse the node name using the more-accepting `DATA` grok pattern.

* Adding sample log entry

* Adding CHANGELOG entry
@ycombinator ycombinator requested a review from a team as a code owner November 18, 2019 11:20
@ycombinator ycombinator requested a review from jsoriano November 19, 2019 03:26
@ycombinator
Copy link
Contributor Author

Travis CI is green and Jenkins CI failures are unrelated. Merging.

1 similar comment
@ycombinator
Copy link
Contributor Author

Travis CI is green and Jenkins CI failures are unrelated. Merging.

@ycombinator ycombinator merged commit c4c4953 into elastic:7.x Nov 19, 2019
@ycombinator ycombinator deleted the backport/7.x/pr-14547 branch November 19, 2019 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants