We are doing one measurment for each netflow exporter. Also we keep only
the data for 60 days ( retention policy on influxdb ). On top of that we
run continuous queries to generate a new measurment for total traffic in/
total traffic in from transit/peers , this are the most used graphs by our
Even with above influxdb still uses ~10G of ram constant. I beleive this
can be optimised if you don't use that many primitives and/or use less
Ram is cheap anyway so for us it does the job.
On Thu, Nov 10, 2016 at 8:43 PM, Raphael Mazelier <r...@futomaki.net> wrote:
> On 10/11/2016 20:58, Catalin Petrescu wrote:
>> Hi Robert,
>> We had good results with grafana and influxdb using below :
>> We export the flow records from pmacctd to kafka then import into influxdb
>> and from there is just a matter of creating the templates. The only
>> thing is kafka to influx , and we use kafka-influxdb with a inhouse
>> parser *
>> (kafka-influxdb). <https://github.com/mre/kafka-influxdb>* take a look
>> * here
> Very interesting. I've made something similar using custom amqp consumer.
> Is influxdb support well as much data ? because you basically insert one ts
> point for one flow entry.
> Raphael Mazelier
> pmacct-discussion mailing list
pmacct-discussion mailing list