We have a mess of transient logging settings defined and wondering if someone can help sort them out:
"transient": {
"logger": {
"index.indexing": "INFO",
"index.search.slowlow": "INFO",
"index.indexing.slowlow": "INFO",
"index.search.slowlog.query": "INFO",
"index.search": "INFO",
"index.indexing.slowlog.index": "INFO",
"index.indexing.slowlog": "INFO",
"index": "INFO",
"index.search.slowlow.query": "INFO",
"index.search.slowlog": "INFO",
"_root": "INFO",
"index.indexing.slowlow.index": "INFO",
"indices": {
"recovery": "DEBUG"
}
}
}
I know that there is no-ability to remove these settings without stopping the entire cluster and then restarting it so looking for a way to fix the settings inheritance in such as way that we can actually modify our settings.
We got into this state because for whatever reason our logging was set to TRACE, despite being defined in elasticsearch.yaml as:
logger:
action: DEBUG
com.amazonaws: WARN
com.amazonaws.jmx.SdkMBeanRegistrySupport: ERROR
com.amazonaws.metrics.AwsSdkMetrics: ERROR
org.apache.http: INFO
discovery: INFO
deprecation: INFO, deprecation_log_file
index.search.slowlog: INFO, index_search_slow_log_file
index.indexing.slowlog: INFO, index_indexing_slow_log_file
additivity:
index.search.slowlog: false
index.indexing.slowlog: false
deprecation: false
Anything we can do to address this issue?