active;1 | activity status |
interface;eth0 | name for the interface |
nick;inet | nick (if given) |
created;1023895272 | creation date in Unix time |
updated;1065467100 | when the database was updated |
totalrx;569605 | all time total received MiB |
totaltx;2023708 | all time total transmitted MiB |
currx;621673719 | latest rx value in /proc |
curtx;981730184 | latest tx value in /proc |
totalrxk;644 | total rx KiB counter |
totaltxk;494 | total tx KiB counter |
btime;1059414541 | system boot time in Unix time |
Then follows 30 lines like the following
d;0;1078696800;559;7433;68;557;1
where d = days, 0 = day number in database (0 is today), 1077314401 date in Unix time, 559 = rx MiB, 7433 = tx MiB, 68 = rx KiB, 557 = tx KiB and 1 tells that vnStat has filled this value and it is in use.
m;0;1078092000;48649;139704;527;252;1 | (x12) |
t;0;1078351200;5979;47155;362;525;1 | (x10) |
h;0;1078699800;118265;516545 | (x24) |
m = months, t = top10 and h = hours, all other fields are in the same order as in days except hours that doesn't have a separate KiB value. For hours the forth and fifth fields have values in KiB.
10 Mbit: | 54 minutes |
100 Mbit: | 5 minutes |
1000 Mbit: | 30 seconds |
However, for 1000 Mbit interfaces updating once every minute is usually still a working option.
Estimated traffic values are likely to be somewhat inaccurate if daily traffic is low because only the MiB counter is used to calculate the estimate.
Virtual and aliased interfaces cannot be monitored because the kernel doesn't provide traffic information for that type of interfaces. Such interfaces are usually named eth0:0, eth0:1, eth0:2 etc. where eth0 is the actual interface being aliased.