OpenSearch/distribution
Jason Tedor fc3280b3cf Expose logs base path
For certain situations, end-users need the base path for Elasticsearch
logs. Exposing this as a property is better than hard-coding the path
into the logging configuration file as otherwise the logging
configuration file could easily diverge from the Elasticsearch
configuration file. Additionally, Elasticsearch will only have
permissions to write to the log directory configured in the
Elasticsearch configuration file. This commit adds a property that
exposes this base path.

One use-case for this is configuring a rollover strategy to retain logs
for a certain period of time. As such, we add an example of this to the
documentation.

Additionally, we expose the property es.logs.cluster_name as this is
used as the name of the log files in the default configuration.

Finally, we expose es.logs.node_name in cases where node.name is
explicitly set in case users want to include the node name as part of
the name of the log files.

Relates #22625
2017-01-16 07:39:37 -05:00
..
deb Remove much ceremony from parsing client yaml test suites (#22311) 2016-12-22 11:00:34 -05:00
integ-test-zip Close and flush refresh listeners on shard close 2017-01-06 20:03:32 -05:00
rpm Remove much ceremony from parsing client yaml test suites (#22311) 2016-12-22 11:00:34 -05:00
src/main Expose logs base path 2017-01-16 07:39:37 -05:00
tar Remove much ceremony from parsing client yaml test suites (#22311) 2016-12-22 11:00:34 -05:00
zip Remove much ceremony from parsing client yaml test suites (#22311) 2016-12-22 11:00:34 -05:00
build.gradle remove double slash from license header 2017-01-05 17:15:34 +01:00