Hello Paolo,

+1 for me, main reasons are the usual Redis ones:

Speed - 100k GET by_id per second
Data persistence across restarts
Multi node deployment is not a MUST like other NoSQL document stores

My use-case is storing time-based events from flows in InfluxDB (bps,
pps, flows per host/subnet) and details (tcp flags, packet sizes,
as_path etc.) in redis. Storing timestamp, tag and value is where Influx
is good, storing documentation is where redis shines.

Storing directly to redis can be usefull, because most of data amount
per flow goes there for me.

The same will apply for InfluxDB but i am interfacing it over http, so
there is bunch of overhead already, i do not think there will be major
performance improvement writing directly, and tag:value pairs are really


On 11/14/2016 06:02 PM, Paolo Lucente wrote:
> Hi Lorenzo,
> You are the second person asking for this - i'd be curious to see on
> the list if there would be anybody else interested in this.
> I have a question, maybe basic: would not Kafka or RabbitMQ be
> integrated the same way with Logstash and/or Telegraf?
> Cheers, Paolo
> On Mon, Nov 14, 2016 at 09:38:57AM +0000, Lorenzo Mainardi wrote:
>> Hi Paolo, I'm writing to asking if you are thinking about
>> supporting Redis as plugin
>> The advantage to use Redis would be that both Logstash both
>> Telegraf support it in a native way, then it would be easy to store
>> pmacct data in native way in Elasticsearch or InfluxDB. Regards
>> digitel
>> Via della Fortezza 6 - 50129 Firenze 
>> www.digitelitalia.com<http://www.digitelitalia.com/> - 800 901 669
>> Ing. Lorenzo Mainardi
>> Tel +39 055 4624933 Fax +39 055 4624 947 
>> l...@digitelitalia.com<mailto:l...@digitelitalia.com>
>> _______________________________________________ pmacct-discussion
>> mailing list http://www.pmacct.net/#mailinglists
> _______________________________________________ pmacct-discussion
> mailing list http://www.pmacct.net/#mailinglists

pmacct-discussion mailing list

Reply via email to