Skip to content

Fix incorrect instructions for disabling deprecation logging #21569

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

Merged
merged 1 commit into from
Nov 15, 2016

Conversation

dakrone
Copy link
Member

@dakrone dakrone commented Nov 15, 2016

We log deprecation events at "WARN", so setting it to info means the events
are still logged. It must be set to error in order to disable the logging.

We log deprecation events at "WARN", so setting it to `info` means the events
are still logged. It must be set to `error` in order to disable the logging.
@dakrone dakrone merged commit 568a7ea into elastic:master Nov 15, 2016
dakrone added a commit that referenced this pull request Nov 15, 2016
We log deprecation events at "WARN", so setting it to `info` means the events
are still logged. It must be set to `error` in order to disable the logging.
dakrone added a commit that referenced this pull request Nov 15, 2016
We log deprecation events at "WARN", so setting it to `info` means the events
are still logged. It must be set to `error` in order to disable the logging.
@dakrone dakrone deleted the fix-deprecation-logger-instructions branch January 23, 2017 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants