Blog

ELK Stack configuration using Ansible

We often receive information from a client that there was an error with the http 500 code on an application. The tester quickly creates a scenario to reproduce the error and another problem arises. Behind a nice frontend there are a dozen or so applications installed on different servers. The error information is undoubtedly in the log - just in which one? You can spend days trying to find the right file on the right server, or you can use a toolkit that allows you to aggregate logs.