Book Image

ElasticSearch Cookbook

By : Alberto Paro
Book Image

ElasticSearch Cookbook

By: Alberto Paro

Overview of this book

ElasticSearch is one of the most promising NoSQL technologies available and is built to provide a scalable search solution with built-in support for near real-time search and multi-tenancy. This practical guide is a complete reference for using ElasticSearch and covers 360 degrees of the ElasticSearch ecosystem. We will get started by showing you how to choose the correct transport layer, communicate with the server, and create custom internal actions for boosting tailored needs. Starting with the basics of the ElasticSearch architecture and how to efficiently index, search, and execute analytics on it, you will learn how to extend ElasticSearch by scripting and monitoring its behaviour. Step-by-step, this book will help you to improve your ability to manage data in indexing with more tailored mappings, along with searching and executing analytics with facets. The topics explored in the book also cover how to integrate ElasticSearch with Python and Java applications. This comprehensive guide will allow you to master storing, searching, and analyzing data with ElasticSearch.
Table of Contents (19 chapters)
ElasticSearch Cookbook
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

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:

  1. To emit every kind of logging ElasticSearch has, you can change the root-level logging from rootLogger: INFO, console, file to rootLogger: DEBUG, console, file

  2. 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...