Ad Widget

Collapse

Forwarding SNMP Traps to existing Trigger definitions

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • nickpiggott
    Junior Member
    • Jan 2023
    • 4

    #1

    Forwarding SNMP Traps to existing Trigger definitions

    Hello,

    I'm running Zabbix 6.2.6 on Ubuntu 22.04LTS, monitoring a set of radio transmitters.

    The transmitters often have short/transient issues, which wouldn't be picked up by SNMP polling, so I have enabled SNMP Traps as well, which are working as expected.

    I have about 50 monitored items (different OIDs) for each transmitter (in a template), and associated about 30 triggers. This is also working as expected, when the polled items change state.

    The SNMP Traps return the same OID/key-value pairs as the monitored items - here's an example of the data received by an SNMP Trap:

    Code:
    20230103.134510 UDP: [192.168.2.3]:32843->[10.8.0.1]:162
    DISMAN-EVENT-MIB::sysUpTimeInstance = 26885995
    SNMPv2-MIB::snmpTrapOID.0 = GATESAIR-DRIVER-MIB::drvEventGpsAlarmLock.0
    GATESAIR-DRIVER-MIB::drvGpsAlarmLock.0 = 1​
    That final line -
    Code:
    GATESAIR-DRIVER-MIB::drvGpsAlarmLock.0 = 1
    ​ - corresponds with an SNMP item that I'm monitoring and that has a trigger associated with it. I can extract that line from the SNMP Trap text using a Regex, but is there any way I can then pass it through the triggers / items without having to duplicate all the trigger state requirements?

    Thanks

    Nick

Working...