Skip to content

Conversation

@alexcams
Copy link
Contributor

@alexcams alexcams commented Oct 27, 2025

Last change on logstash core logger config wires deprecation logger to plain logger by default. It is not needed to duplicate deprecation logs anymore because any call to deprecation_logger.deprecated() will log in plain logger output as well unless user changes this default configuration.

Thanks for contributing to Logstash! If you haven't already signed our CLA, here's a handy link: https://www.elastic.co/contributor-agreement/

Copy link
Member

@jsvd jsvd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's bump the patch version in the gemspec and CHANGELOG so this can be released and included in the next release of Logstash

@alexcams alexcams force-pushed the 18314-remove-deprecation-logger-duplicated-entries branch 2 times, most recently from cc22a60 to 62112b9 Compare October 27, 2025 11:13
@alexcams alexcams force-pushed the 18314-remove-deprecation-logger-duplicated-entries branch from 62112b9 to 12c0ddd Compare October 27, 2025 13:01
@alexcams
Copy link
Contributor Author

let's bump the patch version in the gemspec and CHANGELOG so this can be released and included in the next release of Logstash

@jsvd Done!

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.

2 participants