Using redis with logstash

I am wondering what are the pros and cons of using redis as a broker in the infrastructure?

Currently, all my agents are sending to the central NXLog server, which proxies requests to logstash → ES.

What can I get using a redis server between my nxlog collector and logstash? For me, this seems pointless, since nxlog already has good mem and disk drives in case logstash doesn't work.

What will I get?

thank

+4
source share
5 answers

Under heavy load: an ES (HTTP) call directly can be dangerous, and you may have problems if the ES breaks.

Redis ( ). ES (HTTP).

+1

redis, , . , , .

, logstash, . ( syslog) logstash, .

, redis, logstash, hickups . , (), , syslog, . , logstash, - , ...:)

+1

Logstash Redis . .

Redis ( ), Logstash , "". , .

0

Logstash Redis Redis , (, memcache).

, Logstash, ( ).

, Redis , , logstash.

0

ELK, logstash ( redis). , , . , , redis . " " ( ), redis , .

redis, .

, , redis. , , , , .

, .

0
source

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


All Articles