A closed look at data loss

We talked about data will always be loss, but it’s not always clear to everyone that when and where. Let’s take a pretty simple, 4-step scenario as an example. Below is a minimized service, which involves a set of web servers, running behind a load balancer. Every web server uploads their logs via FileBeat. The logs are then passed to a Logstash service to apply filtering. The filtered logs are then written to ElasticSearch for log search, visualization and monitoring.