[ZBX-5979] ,,Last 20 items'' in dashboard doesn't display discovered triggers Created: 2012 Dec 12  Updated: 2017 May 30  Resolved: 2012 Dec 12

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 2.0.4
Fix Version/s: None

Type: Incident report Priority: Major
Reporter: Wiesław Herr Assignee: Oleg Egorov (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

A little bit of background:
I have a LLD check running to discover filesystems on Linux hosts. The said check includes items and triggers, one of which is a trigger that checks (using nodata()) if the items are constantly updated.
Sometimes a filesystem gets mistakingly unmouted or otherwise inaccessible, so a working trigger is important in this environment.

The problem:
Although the trigger launches a event that is visible on the ,,Events'' screen (I also receive notifications), no info about it is displayed on the main dashboard under the ,,Last 20 items''.
I'm not sure why it would work like that, but think it's related to the fact that ,,The item is not discovered anymore and will be deleted in x days''.

How to reproduce:
1. Add a nodata() check on any item from ,,Discovered filesystems'' LLD
2. Add a new filesystem on a host and wait until it is discovered
3. Remove the filesystem
4. You will get an alert from the nodata() check, it will be listed on the events page, but not on the ,,Last 20 items'' on the dashboard

I'm more than willing to provide additional information on request.



 Comments   
Comment by Oleg Egorov (Inactive) [ 2012 Dec 12 ]

Problem is not in "Last 20", problem is in events.
Because server don't support "disabled" and "Not supported" items.

RESOLVED IN svn://svn.zabbix.com/branches/dev/ZBX-5979 r32105

Comment by Eduards Samersovs (Inactive) [ 2012 Dec 13 ]

Tested

Comment by Oleg Egorov (Inactive) [ 2012 Dec 13 ]

FIXED IN 2.0.5rc1 r32124, 2.1(trunk) r32125
CLOSED

Generated at Fri Mar 29 13:31:11 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.