The event logs are usually our best friends for determining whether a system or its component is experiencing problems. With going away from single node setups we have to say goodbye to finding issues with ease just by reading logs here and there. As the number of nodes increase, it becomes painful to track the status of your deployment. Is there anything that might help? Yes, central logging service. With this approach we can quickly get answers to “why” and “where” something went wrong, even when malfunctioning component is offline, and there is no way to get to its local storage. But deploying a central logging service might turn out to be a little hassle itself. Luckily, you can take advantage of Docker and Ansible in Kolla, enabling you to have a full centralized logging stack in a matter of seconds. During this presentation we will invite you to the Loggingland and compare different containerized approaches - Logstash and Heka, both paired with Elasticsearch and Kibana.
- Advantages and disadvantages of different logging solutions both these that are already mature and these that have recently gained popularity
- How to deploy such solutions
- How to configure your cloud to use centralized logging
- How to get your logs optimally filtered in just few steps
- How to visualize your logs in order to get the answer faster than before