Re: [Xen-users] Dom U bandwidth monitoring - pmacct, bandwidthd?

[Zane Rockenbaugh <zane@xxxxxxxxxxxxxxx>]

Robbie,

Do you have or would you be willing to do a cookbook style write up of setting 
up mrtg for this kind
of monitoring? I've been looking to do just this and grok the basics, but 
haven't found the time to
dig into the config syntax and such.

I little how-to would be greatly appreciated.

Z

Robbie A. Garrett wrote:
> My Company developed a method via mrtg.  Each vm has a vif name that
> means something within our tracking system.
>  
> an example of this would be user32.  On the Xen server, they have a vm
> called user32 and within the config file of the VM, there vif name is
> user32.  We set there MRTG files to pull data based on 'network card
> name' (in this case user32), and use rrd tool to store the
> information.   This makes it very easy to pull all historical data from
> vm's.  When ever a vm moves, so does it's .rrd file  thus keeping all
> bandwidth traffic together.
>  
> This may not solve your issue or question...  but I would try barking up
> the mrtg tree to collect bandwidth totals.
>  
> ------------------------------------------------------------------------
> *From:* xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> [xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Alaa eldin
> [sirash23@xxxxxxxxx]
> *Sent:* Friday, February 12, 2010 11:15 AM
> *To:* Fajar A. Nugraha
> *Cc:* matt@xxxxxxxxxxxxxxxxxx; xen-users@xxxxxxxxxxxxxxxxxxx
> *Subject:* Re: [Xen-users] Dom U bandwidth monitoring - pmacct, bandwidthd?
> 
> every reboot this method " /proc/net/dev " start from zero
> 
> On Fri, Feb 12, 2010 at 11:11 AM, Fajar A. Nugraha <fajar@xxxxxxxxx
> <mailto:fajar@xxxxxxxxx>> wrote:
> 
>     On Fri, Feb 12, 2010 at 11:00 PM, Matthew Law
>     <matt@xxxxxxxxxxxxxxxxxx <mailto:matt@xxxxxxxxxxxxxxxxxx>> wrote:
>     > I would prefer to do this at the egress point rather than run some
>     kind of
>     > accounting process on each dom0.
> 
>     Why? Will you be doing lots of domU moving?
>     The simplest method would be to give each domU a persistent vif name
>     and read their stats from /proc/net/dev
> 
>     --
>     Fajar
> 
>     _______________________________________________
>     Xen-users mailing list
>     Xen-users@xxxxxxxxxxxxxxxxxxx <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx>
>     http://lists.xensource.com/xen-users
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users


-- 
Zane Rockenbaugh
President, Liquid Labs LLC
www.liquid-labs.com

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users