Skip to content

Commit e1c798d

Browse files
Adam Locketoby-sutorqhoxie
authored
[DOCS] Add note to that log4j customization is outside the support scope (#82668) (#83114)
* [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 <adam.locke@elastic.co> Co-authored-by: Quin Hoxie <qhoxie@gmail.com> Co-authored-by: Adam Locke <adam.locke@elastic.co> Co-authored-by: Toby Sutor <55087308+toby-sutor@users.noreply.github.com> Co-authored-by: Quin Hoxie <qhoxie@gmail.com>
1 parent 72690a3 commit e1c798d

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

docs/reference/setup/logging-config.asciidoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,9 @@ If you run {es} from the command line, {es} prints logs to the standard output
1616
[[loggin-configuration]]
1717
=== Logging configuration
1818

19+
IMPORTANT: Elastic strongly recommends using the Log4j 2 configuration that is shipped by default.
20+
21+
1922
Elasticsearch uses https://logging.apache.org/log4j/2.x/[Log4j 2] for
2023
logging. Log4j 2 can be configured using the log4j2.properties
2124
file. Elasticsearch exposes three properties, `${sys:es.logs.base_path}`,

0 commit comments

Comments
 (0)