I am using zabbix 1.3.2beta and a 64bit arch, if this is important in any way.
Taking the delta with ifconfig from the interface within 1 second, i get:
3354500 bytes (per second)
standard within zabbix without multiplier i get in my database
1521950969674 (bytes per second)
now i take a multiplier smaller than 1 (for example 0.1) and i get
268360 (which is pretty much the value of my ifconfig in kbit/s *10)
But zabbix frontend shows me 268,36 KKbit/s, thats not very pretty .. so i have to multiply with 10 to have bits/second...
but a multiplier 10 ends in an entry showing
15219509696740 in my database ..
so multipliers greater/equal 1 are broken
So something's really going crazy here...
Workaround:
use float and a multiplier of 0.000001 .. Make the Units "Mbit/s" and it works for me ..
will try to float around, probably it is a delta/uint-Bug (divisions mostly end in floating point .. interpreting a double as int has strange sideeffects, because the upper and lower part are handled as 2 seperate parts in a float, but as a whole in uint)
Taking the delta with ifconfig from the interface within 1 second, i get:
3354500 bytes (per second)
standard within zabbix without multiplier i get in my database
1521950969674 (bytes per second)
now i take a multiplier smaller than 1 (for example 0.1) and i get
268360 (which is pretty much the value of my ifconfig in kbit/s *10)
But zabbix frontend shows me 268,36 KKbit/s, thats not very pretty .. so i have to multiply with 10 to have bits/second...
but a multiplier 10 ends in an entry showing
15219509696740 in my database ..
so multipliers greater/equal 1 are broken
So something's really going crazy here...

Workaround:
use float and a multiplier of 0.000001 .. Make the Units "Mbit/s" and it works for me ..
will try to float around, probably it is a delta/uint-Bug (divisions mostly end in floating point .. interpreting a double as int has strange sideeffects, because the upper and lower part are handled as 2 seperate parts in a float, but as a whole in uint)
Comment