Re: [openstack-dev] [OpenStack][Neutron][Monasca] Traffic counters at Layer 3

Thanks for replying. Yes, Armando. I've seen it and I'm using that approach to cater explicit labels/traffic the user wants to monitor by providing CIDRs in my plugin's configuration file. However, it gives overall bandwidth for a particular label. I want the traffic going in, out and generated

Re: [openstack-dev] [OpenStack][Neutron][Monasca] Traffic counters at Layer 3

Neutron already supports L3 router with network namespaces which send notifications, as Armando mentioned. Ceilometer can consume these notification and I think monisca can do similar things. I believe you can collect enough information for neutron ovs implementation. 2016-04-25 13:20 GMT-05:00

Re: [openstack-dev] [OpenStack][Neutron][Monasca] Traffic counters at Layer 3

On 25 April 2016 at 11:20, Rubab Syed wrote: > Hi folks, > > I'm writing a plugin for Monasca to monitor traffic at layer 3. My Neutron > backend is OVS and I'm using iptables of network namespaces for getting > traffic counters. Would the following rules in router

[openstack-dev] [OpenStack][Neutron][Monasca] Traffic counters at Layer 3

Hi folks, I'm writing a plugin for Monasca to monitor traffic at layer 3. My Neutron backend is OVS and I'm using iptables of network namespaces for getting traffic counters. Would the following rules in router namespace cover all the traffic at layer 3 per router per tenant? - Chain