All geek questions in one place

What is good architecture for ELK?

I am trying to use ELK to create a log analysis system. I see a lot of architectures that use ELK in different ways. one of them

Logstash-> Redistribution> Logstash-> Elasticseach-> Kibana

The first Logstash is used to collect logs, the second Logstash is used for filter logs.

I'm not very good at Redis, do we need to use this? Why not use Kafka?

+4
source share
3 answers

The redesign between two instances of logstash is a buffer, only there if elasticsearch or the logstash index does not work.

, logstash, . , logstash () , logstash (indexer) . , ( !).

(, syslogs ), , redis rabbitmq, , logstash (indexer).

+3

JSON.

, , , , . , , ELK (http://logz.io/blog/deploy-elk-production/)

0

You can just find a simple ELK Setup ( if doesn't need of Redis). You can go through the link below to fully configure and how to download logs using logstash and search logs using elsticsearch and render in Kibana strong>

Install ELK Installation

0
source

Source: https://habr.com/ru/post/1599110/

More articles:


All Articles