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.5] Fixing node name to use DATA grok pattern (#14547) #14583

Merged
merged 2 commits into from
Nov 20, 2019

Conversation

ycombinator
Copy link
Contributor

Backports the following commits to 7.5:

@ycombinator ycombinator requested a review from a team as a code owner November 18, 2019 11:20
CHANGELOG.next.asciidoc Outdated Show resolved Hide resolved
* 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 merged commit c67ff19 into elastic:7.5 Nov 20, 2019
@ycombinator ycombinator deleted the backport/7.5/pr-14547 branch November 20, 2019 05:32
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…astic#14583)

* Fixing node name to use `DATA` grok pattern (elastic#14547)

* 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

* Fixing CHANGELOG
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