NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter



Using Beaver to Ship Log Files via Redis to Logstash

Beaver’s explicit goal is to provide a shipper that can be used in environments where one or more of the following is true:

  • Operations cannot support the JVM on an instance
  • Developers are more experienced with debugging Python performance issues
  • The server does not have enough memory for a large JVM application
  • Simply shipping logs to an intermediary for later processing is enough

What I’m not very clear about is the need for Redis, but I assume the main reasons could be: 1) logstash doesn’t accept pushed events; or 2) logstash might drop/lose events if pushed to0 fast.

Original title and link: Using Beaver to Ship Log Files via Redis to Logstash (NoSQL database©myNoSQL)