Re: [pmacct-discussion] Redis support

2016-11-14 Thread Lorenzo Mainardi
Da: pmacct-discussion per conto di Paolo Lucente Inviato: lunedì 14 novembre 2016 18.02.19 A: pmacct-discussion@pmacct.net Oggetto: Re: [pmacct-discussion] Redis support Hi Lorenzo, You are the second person asking for this - i'd be curious to see on the list if there would be anybody

Re: [pmacct-discussion] Redis support

2016-11-14 Thread Raphael Mazelier
On 14/11/2016 19:42, Rasto Rickardt wrote: Hello Paolo, +1 for me, main reasons are the usual Redis ones: Pmacct have already a lot of backend plugins, but if another is needed I vote for redis. Redis is blazing fast and can act both as a message queue and a an ephemeral storage. I think

Re: [pmacct-discussion] Redis support

2016-11-14 Thread Rasto Rickardt
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 Lightweight My use-case is storing time-based events from flows in InfluxDB (bps, pps, flows per

Re: [pmacct-discussion] Redis support

2016-11-14 Thread Paolo Lucente
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

[pmacct-discussion] Redis support

2016-11-14 Thread Lorenzo Mainardi
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 dell