Problem with trigger on delta (speed per second) items

[mizaring]

I just installed zabbix 1.4.1 and started to monitor 2 cisco switches. I wanted to know the rate of change for Discarded Input Octets on all my switch ports. Here's my item's configuration for port 101 :

<item type="1" key="ifInDiscards_101" value_type="3">
    <description>Interface 101 Input Discards</description>
    <delay>60</delay>
    <history>90</history>
    <trends>90</trends>
    <units>B / sec</units>
    <delta>1</delta>
    <formula>1</formula>
    <snmp_community>public</snmp_community>
    <snmp_oid>.1.3.6.1.2.1.2.2.1.13.101</snmp_oid>
    <snmp_port>161</snmp_port>
</item>

Then I set a trigger on this item like this :

<trigger>
    <description>Discarded Input Octets On Interface 101 gt; 0 B/s</description>
    <expression>{{HOSTNAME}:ifInDiscards_101.last(0)}gt;0</expression>
    <priority>2</priority>
</trigger>

The problem is Zabbix don't take the calculated value (the rate) but instead it seem to take the raw value received by SNMP. So every interface that has at least one discarded frame (in the counters) will have this trigger set to true. I also tried the following trigger :

<trigger>
    <description>Discarded Input Octets On Interface 101 gt; 0 B/s</description>
    <expression>{{HOSTNAME}:ifInDiscards_101.change(0)}gt;0</expression>
    <priority>2</priority>
</trigger>

But then it seem to take the raw value as the last() value and the calculated value (rate) as the previous value. One way or the other I cannot get a trigger to work with the rate (B/s). Could you please confirm if this is a bug or if it was meant to be this way?

Thanks a lot

[ruedu]

This appears to be the same problem I'm having tracking bandwidth usage.

[Alexei]

Reconfigure this item to calculate Delta (speed per second) instead of using the raw value.

[mizaring]

The item is already configured to calculate the delta (speed per second) (see the xml export in the first post). The problem is not with the item, the rate calculated by zabbix is good and the values saved in the database are the rate.

The problem is when I try to define a trigger on that rate, say I want to activate a trigger when the rate is bigger than 5000 bytes/s, I should set the trigger like this :

{{HOSTNAME}:ifInDiscards_101.last(0)}gt;5000

But this code :

{{HOSTNAME}:ifInDiscards_101.last(0)}

return the raw value from SNMP (the number of discarded input octets) instead of returning the rate calculated by Zabbix. So every port that has more than 5000 discarded input octets in his counters will activate the trigger, even if the rate is below 5000 bytes/sec.

Thanks for looking into this problem

[ruedu]

My items are also configured as deltas.

[tibor]

Mine are delta as well, and I have the same problem.

Running OpenSuse 10.2 x86_64 on a VM. Upgraded from 1.1.7 to 1.4.1.

[Alexei]

Thanks for the details! I will check what's going on here.

[tibor]

Alexei if you need access to a box to help troubleshooting I have a VM image of my setup available that I could NAT for you to use.

[Palmertree]

I am also having the same problem with deltas and triggers.

[Palmertree]

I am not sure if this helps but I am getting delta time triggers going and staying true even when zero is being returned.

{Host:InfInErrors.01.last(0)}>100

InfInErrors -> delta per second

[Palmertree]

It looks like "lastvalue" in the functions table for the associated triggers is showing the mib totals and not the delta change over time. I hope this helps.

[Palmertree]

I think that I found a fix. Please see my patch in the following thread:

http://www.zabbix.com/forum/showthread.php?t=7249

[tibor]

Awesome, I will try it out and let you know.

[Alexei]

The fix is incorrect! Please wait for an official one!