|
[bl ~]# ipvsadm -l -n --stats
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Conns InPkts OutPkts InBytes OutBytes
-> RemoteAddress:Port
TCP 192.168.1.2:80 686986 25647215 0 1474M 0
-> 192.168.1.1:80 233736 8459668 0 499449K 0
-> 192.168.1.1:80 191679 8245615 0 454602K 0
-> 192.168.1.1:80 261571 8941932 0 520763K 0
[bl ~]# ipvsadm -l -n --stats --exact
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Conns InPkts OutPkts InBytes OutBytes
-> RemoteAddress:Port
TCP 192.168.1.2:80 686987 25647233 0 1474815983 0
-> 192.168.1.6:80 233737 8459686 0 499450161 0
-> 192.168.1.5:80 191679 8245615 0 454602010 0
-> 192.168.1.4:80 261571 8941932 0 520763812 0
Thomas Pedoussaut wrote:
> [ Yes I've read
> http://www.austintek.com/LVS/LVS-HOWTO/HOWTO/LVS-HOWTO.monitoring_lvs.html ]
>
> I'm making my own monitoring tools (based on MRTG etc...) and I'm
> currently gathering data from call to ipvsadm --stats -t .....
> That works fairly well but, and there is a but, the cmd line tool does
> some formating like 11234k rather than the full value 11234567 which is
> causing me trouble.
> I tried to access /proc/net/ip_vs* but there is nothing that I could
> use. ip_vs_stats is a general counter, not one per VS.
> For the moment, I reset the counter atfer each read, but it's not great,
> and the day my trafic will grow above the 1M per 5 minutes, I'm f#@4ed.
>
> Any ideas welcome.
>
|
