Changing logging settings (advanced)
Standard logging settings work very well for general usage.
If you need to debug your ElasticSearch server or change how the logging works (that is, remoting send events), you need to change the logging.yml parameters.
Getting ready
You need an installed working ElasticSearch server.
How to do it...
In the config directory in your ElasticSearch, install the directory. There is a logging.yml file which controls the working settings. The steps required for changing the logging settings are:
- To emit every kind of logging ElasticSearch has, you can change the root-level logging from
rootLogger: INFO, console, filetorootLogger: DEBUG, console, file - Now if you start ElasticSearch from command-line (with
bin/elasticsearch –f), you should see a lot of garbage:
How it works...
ElasticSearch logging system is based on the log4j library (http://logging.apache.org/log4j/).
Changing the log level can be useful to check for bugs or understanding malfunctions due to bad configuration or strange plugin behaviors. A verbose log can be used from ElasticSearch community to cover the problems.
This is a powerful library to manage logging, covering all the functionalities of it (it's outside the scope of this book). If a user needs advanced usage, there are a lot of books and articles on the Internet for reference.