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
Under heavy load: an ES (HTTP) call directly can be dangerous, and you may have problems if the ES breaks.
Redis ( ). ES (HTTP).
redis, , . , , .
, logstash, . ( syslog) logstash, .
, redis, logstash, hickups . , (), , syslog, . , logstash, - , ...:)
Logstash Redis . .
Redis ( ), Logstash , "". , .
Logstash Redis Redis , (, memcache).
, Logstash, ( ).
, Redis , , logstash.
ELK, logstash ( redis). , , . , , redis . " " ( ), redis , .
redis, .
, , redis. , , , , .
, .
Source: https://habr.com/ru/post/1535962/More articles:JQuery UI calendar - how to highlight days after current date? - javascriptGo and namespaces: is it possible to achieve something similar to Python? - moduleHow to remove Blend for Visual Studio 2012? - visual-studio-2012OpenGL ES 2.0 - Textures are always black - androidDoing math with LESS variables for animated keyframes - cssA universal subset of regular expressions? Or a comprehensive grammar table of attributes - regexOutputCache with VaryByCustom not working - c #How do compatible class libraries, MVVM, and DDD work? - mvvmSprite Kit Recovery? - iosError reading configuration: Failed to load type ... from assembly 'System.Configuration - c #All Articles