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

Increase visibility of deprecation logger #20254

Merged
merged 2 commits into from Aug 31, 2016
Merged

Increase visibility of deprecation logger #20254

merged 2 commits into from Aug 31, 2016

Conversation

jasontedor
Copy link
Member

The deprecation logger is an important way to make visible features of
Elasticsearch that are deprecated. Yet, the default logging makes the
log messages for the deprecation logger invisible. We want these log
messages to be visible, so the default logging for the deprecation
logger should enable these log messages. This commit changes the log
level of deprecation log message to warn, and configures the deprecation
logger so that these log messages are visible out of the box.

Relates #11033

The deprecation logger is an important way to make visible features of
Elasticsearch that are deprecated. Yet, the default logging makes the
log messages for the deprecation logger invisible. We want these log
messages to be visible, so the default logging for the deprecation
logger should enable these log messages. This commit changes the log
level of deprecation log message to warn, and configures the deprecation
logger so that these log messages are visible out of the box.
@jasontedor jasontedor added review :Core/Infra/Logging Log management and logging utilities v5.0.0-beta1 labels Aug 31, 2016
@nik9000
Copy link
Member

nik9000 commented Aug 31, 2016

LGTM

@clintongormley
Copy link

@jasontedor the main concern was doing this was filling up the disk with millions of deprecation warnings. If the deprecation logger can be size limited and rollover automatically, then I'm good with it.

This commit updates the deprecation logging docs after the default
logging level was changed to warn with all deprecation log messages
emitted at the warn level.
@jasontedor
Copy link
Member Author

If the deprecation logger can be size limited and rollover automatically, then I'm good with it.

We will be able to do this easily with Log4j 2, and I will configure the deprecation logger there to do this.

@jasontedor jasontedor merged commit 1a805bb into elastic:master Aug 31, 2016
@jasontedor jasontedor deleted the warn-deprecation-logger branch August 31, 2016 14:51
This was referenced Aug 31, 2016
@jasontedor
Copy link
Member Author

We will be able to do this easily with Log4j 2, and I will configure the deprecation logger there to do this.

I opened #20287.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Logging Log management and logging utilities >enhancement v5.0.0-beta1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants