Ad Widget

Collapse

Last value in bps not correct

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • verus
    Member
    • Feb 2009
    • 67

    #1

    Last value in bps not correct

    Hello,

    In Zabbix (6.4.1) I made an item to check the incoming and outgoing traffic from some interfaces.
    The thing now is that the values I get are not correct or at least not displayed correctly.

    This is what I get:
    Click image for larger version

Name:	image.png
Views:	424
Size:	5.5 KB
ID:	463664​​
    For example, I get a value of 2836056840

    My configuration is like this:
    Click image for larger version

Name:	image.png
Views:	420
Size:	44.7 KB
ID:	463665

    To me, this configuration seems correct and other configurations are the same but a last value from 2.84 Gbps is not correct. That is much higher than the possibilities of that line.
    I checked if I need to change the units but that seems correct or I don't know what to change.

    On the Zabbix server I get this when I perform an snmpwalk:
    Click image for larger version

Name:	image.png
Views:	703
Size:	2.3 KB
ID:	463666
    So the value is indeed 10 characters.
    Anybody an idea about how I can make this work? Is the "units" wrong?

    Thanks, V.
    Attached Files
  • cyber
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2006
    • 4807

    #2
    Any preprocessing involved?

    Comment

    • verus
      Member
      • Feb 2009
      • 67

      #3
      Originally posted by cyber
      Any preprocessing involved?
      No preprocessing rules are involved:

      Click image for larger version

Name:	image.png
Views:	413
Size:	7.0 KB
ID:	463674

      Comment

      • cyber
        Senior Member
        Zabbix Certified SpecialistZabbix Certified Professional
        • Dec 2006
        • 4807

        #4
        I guess that's your issue...
        You are reading a counter... its evergrowing number. Without proper preprocessing you will not get "values per second".
        Change per second Calculate the value change (difference between the current and previous value) speed per second.
        Evaluated as (value-prev_value)/(time-prev_time), where
        value - current value; prev_value - previously received value; time - current timestamp; prev_time - timestamp of previous value.
        This setting is extremely useful to get speed per second for a constantly growing value. If the current value is smaller than the previous value, Zabbix discards that difference (stores nothing) and waits for another value. This helps to work correctly with, for instance, a wrapping (overflow) of 32-bit SNMP counters.
        Note: As this calculation may produce floating-point numbers, it is recommended to set the 'Type of information' to Numeric (float), even if the incoming raw values are integers. This is especially relevant for small numbers where the decimal part matters. If the floating-point values are large and may exceed the 'float' field length in which case the entire value may be lost, it is actually suggested to use Numeric (unsigned) and thus trim only the decimal part.
        Only one change operation per item is allowed.
        If you mark the Custom on fail checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value, or set a specified error message.

        Comment

      • verus
        Member
        • Feb 2009
        • 67

        #5
        Originally posted by cyber
        I guess that's your issue...
        You are reading a counter... its evergrowing number. Without proper preprocessing you will not get "values per second".
        Change per second Calculate the value change (difference between the current and previous value) speed per second.
        Evaluated as (value-prev_value)/(time-prev_time), where
        value - current value; prev_value - previously received value; time - current timestamp; prev_time - timestamp of previous value.
        This setting is extremely useful to get speed per second for a constantly growing value. If the current value is smaller than the previous value, Zabbix discards that difference (stores nothing) and waits for another value. This helps to work correctly with, for instance, a wrapping (overflow) of 32-bit SNMP counters.
        Note: As this calculation may produce floating-point numbers, it is recommended to set the 'Type of information' to Numeric (float), even if the incoming raw values are integers. This is especially relevant for small numbers where the decimal part matters. If the floating-point values are large and may exceed the 'float' field length in which case the entire value may be lost, it is actually suggested to use Numeric (unsigned) and thus trim only the decimal part.
        Only one change operation per item is allowed.
        If you mark the Custom on fail checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value, or set a specified error message.
        How can I make it right?

        Comment

        • cyber
          Senior Member
          Zabbix Certified SpecialistZabbix Certified Professional
          • Dec 2006
          • 4807

          #6
          Originally posted by verus

          How can I make it right?


          Click image for larger version

Name:	image.png
Views:	404
Size:	351.4 KB
ID:	463745

          Comment

          Working...