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

update log4j2properties.erb for [%node_name]%markers #1

Merged
merged 1 commit into from
Feb 19, 2020

Conversation

sferry
Copy link
Owner

@sferry sferry commented Feb 19, 2020

elasticsearch.log : [2019-06-20T00:45:20,052][WARN ][o.e.c.l.LogConfigurator ] [] Some logging configurations have %marker but don't have %node_name. We will automatically add %node_name to the pattern to ease the migration for users who customize log4j2.properties but will stop this behavior in 7.0. You should manually replace %node_name with [%node_name]%marker in these locations:
/etc/elasticsearch/elastic-elk1/log4j2.properties

This is what this is doing.

Pull request acceptance prerequisites:

  • Signed the CLA (if not already signed)
  • Rebased/up-to-date with base branch
  • Tests pass
  • Updated CHANGELOG.md with patch notes (if necessary)
  • Updated CONTRIBUTORS (if attribution is requested)

elasticsearch.log : [2019-06-20T00:45:20,052][WARN ][o.e.c.l.LogConfigurator  ] [] Some logging configurations have %marker but don't have %node_name. We will automatically add %node_name to the pattern to ease the migration for users who customize log4j2.properties but will stop this behavior in 7.0. You should manually replace `%node_name` with `[%node_name]%marker ` in these locations:
  /etc/elasticsearch/elastic-elk1/log4j2.properties

This is what this is doing.
@sferry sferry merged commit 9d71396 into master Feb 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant