Snmp-trap triggering the same trigger multiple times on the same device.

[Gary.W]

Zabbix 4.2.4 on Centos7

Hi everyone.

I monitored dozens of juniper network devices and used the snmp-trap items to collect trap information from these devices, I recently noticed that some snmp-trap alert messages were not handled correctly.
That is when multiple snmp-traps of different events but same type are generated on one device sent to zabbix-server, but treated as same event by zabbix-server , and given the same event-id , but clearly this is not same event.

Here are my item-key settings and others:

Item
Name：ospfNbrStateChange-test
Type：SNMP trap
Key：snmptrap["ospfNbrStateChange"]


Output information after preprocessing
title：ospfNbrStateChange
nbrouteId: xxx.xxx.12.255
localRID: xxx.xxx.12.253
nbif: xxx.xxx.12.235
status:full⑧


Triggers
Name：ospf-Staus-test
Problem expression：{SNMP traps:snmptrap["ospfNbrStateChange"].str(full⑧)}=0
Recovery expression：{SNMP traps::snmptrap["ospfNbrStateChange"].str(full⑧)}=1






Am I setting the trigger incorrectly? Or what else?
Any suggestions? Or should I report a bug?

Best regards

[sugaretto]

Hello,
Can I ask you how did you configure the traps for the Juniper on Zabbix? Are you using a specific template?

[Gary.W]

Oh Hi，This template for preprocessing snmptrap messages I wrote in javaScript. Later, I may upload to share web.