Changes

Suppose you need to know how much traffic your [[VEcontainer]]s eat. It can be easily done

Let's consider the very simple situation: one VE container with one IP address on the [[Hardware Node]]with only one network interface. To be more exact, assume that [[VEcontainer]] ID is <tt>200</tt>, the IP address of the [[HN]]is <tt>192.168.0.56</tt>, the network interface name is <tt>eth0</tt>, and the IP address of the [[VEcontainer]] is <tt>192.168.0.117</tt>.

You wish to know how much many bytes VE container 200 eats. One more assumption is that there are no iptables rules

Almost any traffic that goes to and from a VE container can be catched by FORWARD chain of iptables module in [[VE0container0]],

To obtain current traffic usage of VE container you can issue the command:

'''Bytes''' column is the column we need. It's worth to saysaying, that restarting a VE container doesn't affect accounting,

As If you want to process the results with a script it is easy useful to see, it's not peruse the "-x" or "--exact" option of iptables<pre># iptables -VE statistic, but rather pernvx -IP statistic. Thus you must be carefulL FORWARD</pre>then changing VE IP addressesYou will get the exact value of the packet and byte counters, otherwise you'll get mess instead of only the rounded number in K’s (multiples of 1000) M’s (multiples of 1000K) or G’s (multiples of results 1000M).

As is easy to see, it's not per-container statistic, but rather per-IP statistic. Thus you must be carefulthen changing container IP addresses, otherwise you'll get mess of results. By saying ''almost any traffic'' I mean that traffic between a [[VEcontainer]] and [[VE0container0]] is not accounted by rules above.

# iptables -nv nvx -L INPUT

# iptables -nv nvx -L OUTPUT

The disadvantage is that doing by doingit this way you zero all counters in all rules. If it is not what you need,

# iptables -nv nvx -L FORWARD

# iptables -nv nvx -L FORWARD

; More than one VE container on the node: Just add the rules like above for each VE container IP.

; More than one IP per VEcontainer.: For each IP add the rules like above. When counting the complete traffic of a VE container you have to summarize over all IPs that this VE container owns.

first a small script to get === Get CTIDs of all vz id's for later onrunning containers ===

vzlist |grep run|tr -s [:blank:]H -oveid |cut -dsed ' s/ //g;' -f2

second a small script witch get === Get all ip's IPs of running vz'scontainers ===

for i in `./vzvzlist -allH -running`; do vzctl exec $i ifconfig |grep 'venet0:0' -A1|tail -n1|cut -d':' -f2|cut -d' ' -f1; doneo ip

and a small script to set === Set up all iptable needed iptables rules===

for i in `./vz-all-running-ip`; do iptables -D FORWARD -s $i; iptables -D FORWARD -d $i; done >/dev/null 2>/dev/null&1for i in `./vz-all-running-ip`; do iptables -A FORWARD -s $i; iptables -A FORWARD -d $i; done >/dev/null 2>&1</pre> === Generate a traffic.log ===Please use crontab to run this script once per hour or day to collect your traffic statistics. (Warning, the counters can overflow if there is too much traffic within that period. Would recommend 15 minute intervals if you expect a lot of traffic)<pre>host2:~/bin# cat vz-generate-traffic-logtrafficlog="/var/log/vz-traffic.log"for i in `./vz-all-running-ip` ; do echo -n `date "+%Y-%m-%d %H:%M:%S"` >> $trafficlog echo -n " $i " >> $trafficlog echo `iptables -nvx -L FORWARD | grep " $i " | tr -s [:blank:] |cut -d' ' -f3| awk '{sum+=$1} END {print sum;}'` >> $trafficlog done # reset the counter iptables -Z # update the iptables rules if there is a any change in containers ./vz-iptables-create-rules  # copy the trafficlog file to a webserver where users can see their traffic  # please mind to use # ssh-keygen -t rsa # to generate ssh keys # and append the new public key from your hardware node (~/.ssh/id_rsa.pub) # to ~/.ssh/authorized_keys2 on the HOST-TO-SHOW-THE-TRAFFIC-TO-THE-USERS # in order for the below scp command to not ask for root password scp $trafficlog USER@HOST-TO-SHOW-THE-TRAFFIC-TO-THE-USERS:/var/www/OPENVZ-CONTROL-WEB-SITE/tmp/$HOSTNAME-traffic # clear the copied trafficlog cp /dev/null $trafficlog # start a php script to store the traffic in a MySQL Database on the HOST-TO-SHOW-THE-TRAFFIC-TO-THE-USERS # please mind to use .htaccess to secure this wget -q http://HOST-TO-SHOW-THE-TRAFFIC-TO-THE-USERS/traffic-read.php?HN=$HOSTNAME -O /dev/null