[ZBX-11237] Trigger shows up in dashboard, but trigger condition not present Created: 2016 Sep 19  Updated: 2017 May 30  Resolved: 2016 Sep 20

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 3.2.0
Fix Version/s: None

Type: Incident report Priority: Minor
Reporter: Adrian Pinzari Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: triggers
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS Linux release 7.2.1511 (Core)/Apache 2.4.6-40/PHP 5.4.16-36


Attachments: JPEG File 2016-09-19 10_48_18-The King's University_ Dashboard.jpg     JPEG File 2016-09-19 10_55_04-The King's University_ History [refreshed every 30 sec.].jpg     JPEG File 2016-09-19 10_55_23-The King's University_ Configuration of triggers.jpg    

 Description   

We have created multiple ICMP templates with different check times after we upgraded to 3.2.

One of the hosts shows the trigger state as problem for the icmp ping loss item, however if we check latest data and problem history - there is no issue (see screenshots attached)



 Comments   
Comment by richlv [ 2016 Sep 19 ]

from the screenshots, there does not seem to be an indication of a bug yet - we don't see filter settings etc.
it would probably be best to discuss in the support channels as per http://zabbix.org/wiki/Getting_help and return here if it is determined that there indeed is a bug.

Comment by Adrian Pinzari [ 2016 Sep 19 ]

Thank you.

We will open the discussion on the forum. I'm not sure what filters you're referring to though. The Ping loss is too high on Exchange CAS Array is being shown as a problem state (Warning). Even though the trigger configuration (backed up by the graph) does indicate that the value is not near the trigger condition.

This has started after the 3.2 update without any similar issues for the last 2 years we've been running Zabbix.

Comment by Adrian Pinzari [ 2016 Sep 19 ]

I guess issue can be closed for now. We un-linked the template and cleared all items and re-linked it. It may not have liked being linked with a template that had the same item keys. I'm not 100% sure.

Generated at Wed Apr 09 04:43:11 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.