Ad Widget

Collapse

Trigger for burst traffic on network link

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ebais
    Junior Member
    • Jan 2011
    • 3

    #1

    Trigger for burst traffic on network link

    Hi,

    I'm trying to figger out how to set the correct value in a trigger to get a warning when a link is having burst traffic.

    However I'm having some difficulties in the traffic calculations (Octets) vs Mbit's and what I'm seeing in Zabbix.

    Let's say I want to put a trigger on a link when it is doing more than 50Mbit per second for at least 900 seconds (15 minutes) and I poll the interface every 30 seconds.

    50 Mbit/s -> 50 x 1000
    50.000 Kbit/s -> 50000 x 1000
    50.000.000 bit/s -> 50000000 / 8
    6.250.000 byte/s (or octet)

    Now if I want to have a trigger after 900 seconds of 50Mbit p/s. I think one should do 900 * 6250000 = 5625000000 octets

    Question that I have:

    Is the above correct ?
    Should I put the following in the trigger ? {switch1:ifInOctets.1006.min(900)}> 5625000000
    or should I put the number of octets per 30 seconds in the trigger ? like : {switch1:ifInOctets.1006.min(900)}> 187500000

    And .. is the used expression .min(seconds) the correct one to us ?

    Thanks in advance for a reply,
    Erik
  • alixen
    Senior Member
    • Apr 2006
    • 474

    #2
    Hi,

    You have not described how ifInOctets.1006 item is defined, so I suppose that it is:
    • Custom multiplier : None
    • Store value : Delta (speed per second)

    So you are actually storing octets/s (or bytes/s).

    In this case your trigger is:
    {switch1:ifInOctets.1006.min(900)}>6250000

    You can also directly work with bits/s with a different setup:
    ifInOctets.1006:
    • Custom multiplier : 8
    • Units : b/s
    • Store value : Delta (speed per second)

    You are then storing bits/s and your trigger will be:
    {switch1:ifInOctets.1006.min(900)}>50000000

    I prefer second setup since I am used to bits/s for link speeds.

    Regards,
    Alixen
    http://www.alixen.fr/zabbix.html

    Comment

    • ebais
      Junior Member
      • Jan 2011
      • 3

      #3
      Hi Alixen,

      This is how the interface is configured :

      Units bps
      Use custom multiplier 8
      Update interval (in sec) 30
      Store value As is Delta (speed per second)Delta (simple change)

      So my problem in the trigger is that the info was already converted into bps instead of working with octets

      Thanks for the tip.
      I'll try this out.

      Erik

      Comment

      • alixen
        Senior Member
        • Apr 2006
        • 474

        #4
        Hi,

        Originally posted by ebais
        Store value As is Delta (speed per second)Delta (simple change)
        Which one ?
        your formula will be highly dependent on the way you store your data !

        Regards,
        Alixen
        http://www.alixen.fr/zabbix.html

        Comment

        • ebais
          Junior Member
          • Jan 2011
          • 3

          #5
          It is stored using the following :

          Store value Delta (speed per second)

          Sorry the copy / paste was incorrect due to the drop-down being copied as well.

          Comment

          • alixen
            Senior Member
            • Apr 2006
            • 474

            #6
            Originally posted by ebais
            It is stored using the following :

            Store value Delta (speed per second)

            Sorry the copy / paste was incorrect due to the drop-down being copied as well.
            So you are already storing bits/s.
            {switch1:ifInOctets.1006.min(900)}>50000000
            should be OK.

            regards,
            Alixen
            http://www.alixen.fr/zabbix.html

            Comment

            Working...