From 30b8cdc18409baf46cb4996ec11d8c6f5418d64e Mon Sep 17 00:00:00 2001 From: Toby Sutor <55087308+toby-sutor@users.noreply.github.com> Date: Tue, 25 Jan 2022 23:03:16 +0100 Subject: [PATCH] [DOCS] Add note to that log4j customization is outside the support scope (#82668) * [docs] Add note to Elasticsearch logging that log4j customization is out of support scope * Update language for default logging recommendation Co-authored-by: Adam Locke Co-authored-by: Quin Hoxie Co-authored-by: Adam Locke --- docs/reference/setup/logging-config.asciidoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/reference/setup/logging-config.asciidoc b/docs/reference/setup/logging-config.asciidoc index d744b61491c9a..8ef1e7223eaf2 100644 --- a/docs/reference/setup/logging-config.asciidoc +++ b/docs/reference/setup/logging-config.asciidoc @@ -14,6 +14,9 @@ If you run {es} from the command line, {es} prints logs to the standard output [[loggin-configuration]] === Logging configuration +IMPORTANT: Elastic strongly recommends using the Log4j 2 configuration that is shipped by default. + + Elasticsearch uses https://logging.apache.org/log4j/2.x/[Log4j 2] for logging. Log4j 2 can be configured using the log4j2.properties file. Elasticsearch exposes three properties, `${sys:es.logs.base_path}`,