Hello,
We're having issues with equipment that cannot separate inbound/outbound
traffic using sflow V5.
Looking at the sflow V5 protocol it's having the following fields.
Usually they match the snmp interface indexes.
/source_id/
/interface input/
/interface output/
What I suggest as a new
Hi Jordan,
not sure what you mean with “equipment that cannot separate inbound/outbound
traffic” but as long as you have direction in your flow data you can add a
pre-tag map like
!
! tag=1 - inbound IPv4 traffic
! tag=2 - outbound IPv4 traffic
! tag=3 - inbound IPv6 traffic
! ta
Hi List,
Maybe someone can point out what I am doing wrong. I am trying to get nfacctd to
only do inserts and not do updates
but my data looks like it is still doing updates, see row from pgsql below:
tag | ip_src | ip_dst | port_src | port_dst | ip_proto | tos |
packets |
Hello,
we use nfacctd to account our customers inbound/outbound traffic with
dst_net,dst_mask/src_net,src_mask aggregation, but if the networks_file
list contains networks like:
10.0.0.0/26
10.0.0.0/24
10.0.0.0/22
and traffic goes to some IP belonging to 10.0.0.0/26, it only accounted
for 10
Hello,
I mean that when you enable sflow on an interface you cannot configure
ingress/egress option.
It captures both directions while we need only data for ingress traffic.
There are two major problems with your solution. I think /direction /is
not a valid sfacct key and we already use preta
Hi all,
Wondering if anyone has a simillar problem with kafka plugin. nfacctd
dosn't send to kafka , using :
conf
---
kafka_topic: pmacct1
kafka_topic[test]: pmacct1
kafka_refresh_time[test]: 300
kafka_history[test]: 5m
kafka_history_roundoff[test]: m
---
logs:
Jul 27 23:55:01 DEBUG ( test/kafka
Hi Mehul
> Is there any configuration to start/stop accounting at run time ?
In Pmacct only by using maps + filtering and recreating + reloading the maps
for changes at runtime. For all I know - there is no API provided by Pmacct for
that and there is no way implemented to trigger actions based
Hi,
just my 2 cents.
I found very useful InfluxDB (https://influxdata.com/) for time-series
data storage. It is extremely fast and lean on storage questions, uses
kind of 20 bytes per record.
Combining with Grafana (http://grafana.org/) you can build classy and
stylish user interface.
Currently