Hi everybody,
is use the sflow collector and want to collect sflow data depending on the inteface information which is possible since version 0.12.1.
The importat columns are in_iface and out_iface as you can see in the aggregate part.
-
aggregate: tag,tag2,in_iface,
Hi everybody,
is use the sflow collector and want to collect sflow data depending
on the inteface information which should be possible since version 0.12.1.
The importat columns are in_iface and out_iface as you can see in the
aggregate part.
-
aggregate:
Hi Bernd,
If i get it correctly, you should be referring to the big 1073741823
and 2147483648 values in your SQL table. According to the sFlow (v5)
specifications, these values are perfectly valid:
1073741823 = 0x3FFF: [ ... ] this is used in describing traffic
which is not bridged, routed,
Hi,
I'm using pmacct 0.12.1 with PostgreSQL 8.4 and FloX. i'm running pmacctd
and nfacctd daemons (probe and collector).
After 1 day running, I'm getting 1+min to make a query.
Is there any config in pmacct and PostgreSQL that I can do improve this?
Here is my config in pmacct:
pmacctd.conf:
Hi Sergio,
I don't know FloX very well - hence would be good information to know
which specific SQL queries are performing bad. Maybe there is room to
improve indexing.
Is it also your goal to store every micro-flow into the SQL database?
Any chance a more compact aggregation method would fit
Hi Paolo,
I'm getting low perfomance while selecting from psql and from FloX.
For example, selecting * WHERE ip_src = 'x.x.x.x'
How can I do a more compact aggregation? You mean by getting samples ?
Actually, I did not understand very well sql_history and roundoff concepts,
but increasing
