Deprecation logging -- logger level

Elastic Stack Elasticsearch
1

Hi,
Just wanted to understand if there is any difference in terms of the message content if the level is set to WARN or INFO for deprecation logging?

For e.g

{
  "persistent": {
    "logger.org.elasticsearch.deprecation": "<logger level>"
  }
}
2

Yes, there should be. Info provide more details than Warn. Check the documentation.

3

Hi,
I did see that doc, but it makes no mention of INFO level actually, which brings me to some questions. (Using SaaS Elasticsearch)

  • If we do not set anything in logger.org.elasticsearch.deprecation, does it mean it will still write deprecation logs by default?
  • If we do set any forms of logger level, e.g INFO, how does it then affect the log levels given the explanation below says it emits at CRTITCAL level and then sometimes it emits at WARN level if feature is less critical.

Elasticsearch also writes deprecation logs to the log directory. These logs record a message when you use deprecated Elasticsearch functionality. You can use the deprecation logs to update your application before upgrading Elasticsearch to a new major version.
By default, Elasticsearch rolls and compresses deprecation logs at 1GB. The default configuration preserves a maximum of five log files: four rolled logs and an active log.
Elasticsearch emits deprecation log messages at the CRITICAL level. Those messages are indicating that a used deprecation feature will be removed in a next major version. Deprecation log messages at the WARN level indicates that a less critical feature was used, it won’t be removed in next major version, but might be removed in the future.