honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/core/config/logging.yml

82 lines
2.4 KiB
YAML
Raw Normal View History

Allow to configure root logging level using system properties. Ex. -Des.logger.level=DEBUG . Defaults to INFO as before.
2013-08-15 08:35:23 -04:00
# you can override this using by setting a system property, for example -Des.logger.level=DEBUG
es.logger.level: INFO
rootLogger: ${es.logger.level}, console, file
initial commit
2010-02-08 08:30:06 -05:00
logger:
reafactor how actions handle failures, better response when non active shards exists, also, default logging to have action set to DEBUG so exceptions in actions are logged in the server
2010-04-06 18:54:33 -04:00
# log action execution errors for easier debugging
more work on reusing work node level data, now when recovering from peers
2010-06-24 08:34:02 -04:00
action: DEBUG
Infra for deprecation logging Add support for a specific deprecation logging that can be used to turn on in order to notify users of a specific feature, flag, setting, parameter, ... being deprecated. The deprecation logger logs with a "deprecation." prefix logge (or "org.elasticsearch.deprecation." if full name is used), and outputs the logging to a dedicated deprecation log file. Deprecation logging are logged under the DEBUG category. The idea is not to enabled them by default (under WARN or ERROR) when running embedded in another application. By default they are turned off (INFO), in order to turn it on, the "deprecation" category need to be set to DEBUG. This can be set in the logging file or using the cluster update settings API, see the documentation Closes #11033
2015-05-26 11:44:52 -04:00
# deprecation logging, turn to DEBUG to see them
deprecation: INFO, deprecation_log_file
remove cloud plugin, reimplement an AWS specific cloud plugin with S3 gateway and EC2 discovery
2010-07-24 16:39:43 -04:00
# reduce the logging for aws, too much is logged under the default INFO
com.amazonaws: WARN
Reduce cloud-aws logging when rootLogger is DEBUG
2014-12-09 15:39:37 -05:00
org.apache.http: INFO
more work on reusing work node level data, now when recovering from peers
2010-06-24 08:34:02 -04:00
# gateway
#gateway: DEBUG
#index.gateway: DEBUG
# peer shard recovery
Peer recovery: Allow to throttle recovery based on "size per sec", closes #1304.
2011-09-06 05:40:14 -04:00
#indices.recovery: DEBUG
initial commit
2010-02-08 08:30:06 -05:00
reformat the default config file, add more comments
2011-07-20 16:29:25 -04:00
# discovery
#discovery: TRACE
Index shard search slow log (query and fetch), closes #1462.
2011-11-14 07:10:39 -05:00
index.search.slowlog: TRACE, index_search_slow_log_file
Indexing Slow Log closes #2457
2012-12-03 04:21:59 -05:00
index.indexing.slowlog: TRACE, index_indexing_slow_log_file
Index shard search slow log (query and fetch), closes #1462.
2011-11-14 07:10:39 -05:00
additivity:
index.search.slowlog: false
Indexing Slow Log closes #2457
2012-12-03 04:21:59 -05:00
index.indexing.slowlog: false
Infra for deprecation logging Add support for a specific deprecation logging that can be used to turn on in order to notify users of a specific feature, flag, setting, parameter, ... being deprecated. The deprecation logger logs with a "deprecation." prefix logge (or "org.elasticsearch.deprecation." if full name is used), and outputs the logging to a dedicated deprecation log file. Deprecation logging are logged under the DEBUG category. The idea is not to enabled them by default (under WARN or ERROR) when running embedded in another application. By default they are turned off (INFO), in order to turn it on, the "deprecation" category need to be set to DEBUG. This can be set in the logging file or using the cluster update settings API, see the documentation Closes #11033
2015-05-26 11:44:52 -04:00
deprecation: false
Index shard search slow log (query and fetch), closes #1462.
2011-11-14 07:10:39 -05:00
initial commit
2010-02-08 08:30:06 -05:00
appender:
console:
type: console
layout:
type: consolePattern
add date by default to logs outputted
2010-09-15 17:04:47 -04:00
conversionPattern: "[%d{ISO8601}][%-5p][%-25c] %m%n"
initial commit
2010-02-08 08:30:06 -05:00
file:
type: dailyRollingFile
file: ${path.logs}/${cluster.name}.log
datePattern: "'.'yyyy-MM-dd"
layout:
type: pattern
Truncate log messages at 10,000 characters
2015-05-07 17:53:29 -04:00
conversionPattern: "[%d{ISO8601}][%-5p][%-25c] %.10000m%n"
Index shard search slow log (query and fetch), closes #1462.
2011-11-14 07:10:39 -05:00
[DOCS] Added documentation for log4j-extras dependency
2014-11-13 05:29:48 -05:00
# Use the following log4j-extras RollingFileAppender to enable gzip compression of log files.
# For more information see https://logging.apache.org/log4j/extras/apidocs/org/apache/log4j/rolling/RollingFileAppender.html
#file:
#type: extrasRollingFile
Fix example in logging daily rotate configuration PR #8464 come with a bug in the example provided. First, the current log file is not compressed so it should not end with `.gz`. Second, conversion pattern was removing all the log content but was printing only the log date. Then, the current log filename was hardcoded to `elasticsearch` instead of the cluster name.
2014-11-19 09:49:37 -05:00
#file: ${path.logs}/${cluster.name}.log
[DOCS] Added documentation for log4j-extras dependency
2014-11-13 05:29:48 -05:00
#rollingPolicy: timeBased
Fix example in logging daily rotate configuration PR #8464 come with a bug in the example provided. First, the current log file is not compressed so it should not end with `.gz`. Second, conversion pattern was removing all the log content but was printing only the log date. Then, the current log filename was hardcoded to `elasticsearch` instead of the cluster name.
2014-11-19 09:49:37 -05:00
#rollingPolicy.FileNamePattern: ${path.logs}/${cluster.name}.log.%d{yyyy-MM-dd}.gz
[DOCS] Added documentation for log4j-extras dependency
2014-11-13 05:29:48 -05:00
#layout:
#type: pattern
Fix example in logging daily rotate configuration PR #8464 come with a bug in the example provided. First, the current log file is not compressed so it should not end with `.gz`. Second, conversion pattern was removing all the log content but was printing only the log date. Then, the current log filename was hardcoded to `elasticsearch` instead of the cluster name.
2014-11-19 09:49:37 -05:00
#conversionPattern: "[%d{ISO8601}][%-5p][%-25c] %m%n"
[DOCS] Added documentation for log4j-extras dependency
2014-11-13 05:29:48 -05:00
Infra for deprecation logging Add support for a specific deprecation logging that can be used to turn on in order to notify users of a specific feature, flag, setting, parameter, ... being deprecated. The deprecation logger logs with a "deprecation." prefix logge (or "org.elasticsearch.deprecation." if full name is used), and outputs the logging to a dedicated deprecation log file. Deprecation logging are logged under the DEBUG category. The idea is not to enabled them by default (under WARN or ERROR) when running embedded in another application. By default they are turned off (INFO), in order to turn it on, the "deprecation" category need to be set to DEBUG. This can be set in the logging file or using the cluster update settings API, see the documentation Closes #11033
2015-05-26 11:44:52 -04:00
deprecation_log_file:
type: dailyRollingFile
file: ${path.logs}/${cluster.name}_deprecation.log
datePattern: "'.'yyyy-MM-dd"
layout:
type: pattern
conversionPattern: "[%d{ISO8601}][%-5p][%-25c] %m%n"
Index shard search slow log (query and fetch), closes #1462.
2011-11-14 07:10:39 -05:00
index_search_slow_log_file:
type: dailyRollingFile
file: ${path.logs}/${cluster.name}_index_search_slowlog.log
datePattern: "'.'yyyy-MM-dd"
layout:
type: pattern
conversionPattern: "[%d{ISO8601}][%-5p][%-25c] %m%n"
Indexing Slow Log closes #2457
2012-12-03 04:21:59 -05:00
index_indexing_slow_log_file:
type: dailyRollingFile
file: ${path.logs}/${cluster.name}_index_indexing_slowlog.log
datePattern: "'.'yyyy-MM-dd"
layout:
type: pattern
conversionPattern: "[%d{ISO8601}][%-5p][%-25c] %m%n"