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.

Sign up for GitHub

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

Jump to bottom

add logging breaking changes from 5.3 to 6.0 #31583

Merged
merged 1 commit into from
Jun 27, 2018
Merged

add logging breaking changes from 5.3 to 6.0 #31583

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions docs/reference/migration/migrate_6_0/packaging.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,3 +87,17 @@ environment used to start Elasticsearch (and various supporting scripts). This
legacy feature could be useful when there were several environment variables
useful for configuring JVM options; this functionality had previously been
replaced by <<jvm-options>>. Therefore, `ES_INCLUDE` has been removed.

==== Logging configuration

Previously Elasticsearch exposed a single system property (`es.logs`) that
included the absolute path to the configured logs directory, and the prefix of
the filenames used for the various logging files (the main log file, the
deprecation log, and the slow logs). This property has been replaced in favor of
three properties:

* `es.logs.base_path`: the absolute path to the configured logs directory
* `es.logs.cluster_name`: the default prefix of the filenames used for the
various logging files
* `es.logs.node_name`: exposed if `node.name` is configured for inclusion in
the filenames of the various logging files (if you prefer)