We are planning to add support in the next release of Filebeat for regexp, that will reduce the number of logs. I'll come back to you when we finish with the implementation, so maybe you want to try one of our nightlies before the release date.
Hi Monica
Thanks. Would wait for the next release.
But my question is more on the architecture - whether my current setup could handle the load or need any intermediary Queuing system to ensure the load is balanced or throttled.
Not sure if this is the correct category for this query..
Redis output is deprecated and we encourage our Filebeat users to send data directly to Logstash. In 3.x release, we are planning to add persistent queuing in Logstash (https://github.com/elastic/logstash/issues/2605) and an additional queuing system will not be needed anymore.
totally unrelated to your problem. Please create a new topic. Message queue is optional + redis has been renewed for 5.x release (complete rewrite). Logstash problem due to pipeline in logstash being blocked by output or very slow filter.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.